Hmm … interesting question. I also take days off when I need it. Usually so I can recharge and refocus. So far this has been helpful. I’m still trying to get better at being proactive about taking test days. Sometimes I’ll work really hard for a long period of time and then crash and burn. After that I’ve got to “get back on the horse”. I think it’d be better if I planned rest days in advance.
Another solution that comes to mind (as I type) is to set clearly defined goals or tasks for your study session. For example, I will set a timer and study for 1 hour. Then when the timer ends I will stop studying and do something else (ideally something that’s good for your overall physical/mental health like exercise or socializing or another hobby).
Another thing to consider is how you feel about what you’re working on. Assuming it’s a project of your choosing, if you feel like you have to “drag” yourself to it to work on it, then maybe you need to consider a different project.
If you’re finding parts of it challenging, then break down what parts your struggling with and find out how you can learn more about those parts.
Those are my ideas. If you or others have other ideas, I’d be interested in hearing them. 😊
Thank you very much for your astute input. It's really got me thinking of my entire process.
I'm the same as you in the fact that I'll go really hard for a period of time and when I eventually burnout I get a repulsive reaction from even looking at VSCode.
The project I'm doing is completely interesting to me because it's the first complete ReactJS project in doing. I think I just take long strides that eventually get me tired.
I'll definitely draw up a schedule I can use per day to lessen the effects of my burnout. Thank you🙏🏾
You’re welcome ☺️ I’m glad you found my thoughts 💭 helpful. Your insightful question has given me pause and allowed me to self-reflect in my own study habits so thank you 🙏🏼 for that.
Assuming it’s a project of your choosing, if you feel like you have to “drag” yourself to it to work on it, then maybe you need to consider a different project.
Unfortunately, nothing of notable value would ever get done if this were the approach to software development. Sometimes the only solution/option is to stubbornly plow through all of the problems head on but the decision to have that mindset has to be internalized and permeate the deepest depths of the person. It's not something that can be taught or forced upon someone.
I do agree that every software project can be broken down into tasks and those tasks can further be broken down into subtasks once they are being worked on. It isn't a good idea to prematurely break down tasks into subtasks or the list of tasks will be overwhelming to look at. Smaller victories over a longer period of time lead to completed tasks and completed tasks ultimately lead to a completed project.
I don't think burnout is something that can be "cured" but rather something to rest and recover from. I'd be very skeptical with ways of dealing with it that don't involve some form of rest and recovery.
This article from psyche.co is one of my favourite resources on this, it's worth a read.
I've known rest is important but have struggle to integrate into my routine in any reliable way. This article has given me some ideas on how to better incorporate rest into my work/study routine. Thanks for sharing.
Hmm … interesting question. I also take days off when I need it. Usually so I can recharge and refocus. So far this has been helpful. I’m still trying to get better at being proactive about taking test days. Sometimes I’ll work really hard for a long period of time and then crash and burn. After that I’ve got to “get back on the horse”. I think it’d be better if I planned rest days in advance.
Another solution that comes to mind (as I type) is to set clearly defined goals or tasks for your study session. For example, I will set a timer and study for 1 hour. Then when the timer ends I will stop studying and do something else (ideally something that’s good for your overall physical/mental health like exercise or socializing or another hobby).
Another thing to consider is how you feel about what you’re working on. Assuming it’s a project of your choosing, if you feel like you have to “drag” yourself to it to work on it, then maybe you need to consider a different project.
If you’re finding parts of it challenging, then break down what parts your struggling with and find out how you can learn more about those parts.
Those are my ideas. If you or others have other ideas, I’d be interested in hearing them. 😊
Thank you very much for your astute input. It's really got me thinking of my entire process.
I'm the same as you in the fact that I'll go really hard for a period of time and when I eventually burnout I get a repulsive reaction from even looking at VSCode.
The project I'm doing is completely interesting to me because it's the first complete ReactJS project in doing. I think I just take long strides that eventually get me tired.
I'll definitely draw up a schedule I can use per day to lessen the effects of my burnout. Thank you🙏🏾
You’re welcome ☺️ I’m glad you found my thoughts 💭 helpful. Your insightful question has given me pause and allowed me to self-reflect in my own study habits so thank you 🙏🏼 for that.
My pleasure bro🤝
Continue slaying and doing the things you do🔥
Unfortunately, nothing of notable value would ever get done if this were the approach to software development. Sometimes the only solution/option is to stubbornly plow through all of the problems head on but the decision to have that mindset has to be internalized and permeate the deepest depths of the person. It's not something that can be taught or forced upon someone.
I do agree that every software project can be broken down into tasks and those tasks can further be broken down into subtasks once they are being worked on. It isn't a good idea to prematurely break down tasks into subtasks or the list of tasks will be overwhelming to look at. Smaller victories over a longer period of time lead to completed tasks and completed tasks ultimately lead to a completed project.
I don't think burnout is something that can be "cured" but rather something to rest and recover from. I'd be very skeptical with ways of dealing with it that don't involve some form of rest and recovery.
This article from psyche.co is one of my favourite resources on this, it's worth a read.
I've known rest is important but have struggle to integrate into my routine in any reliable way. This article has given me some ideas on how to better incorporate rest into my work/study routine. Thanks for sharing.
Thank you for that!