Preventing burnout for programmers — Medium
https://medium.com/@karolisram/preventing-burnout-for-programmers-12b4968adbaa
https://medium.com/@karolisram/preventing-burnout-for-programmers-12b4968adbaa
Medium
Preventing burnout for programmers
It’s not rare in the field of programming to burn out and lose passion for your work. Just look at all these questions that arise, and the…
Forwarded from URL Reader
* [Burnout amongst developers: an industry disease?]( /read_oF0TsfJ)
These articles act as an evidence that burnout is a real and common phenomenon in IT industry. Having dealt with burnout myself, I wanted to explore this issue deeper and help others deal with it or even prevent it in the first place.
### Why burnout happens
Burnout seems to occur amongst the programmers more often than professionals in other fields. I don’t have a definite answer as to why this happens, but I suspect there are four main reasons.
1. The first one is **physical**. Sitting at your desk, in front of the computer every day, is unhealthy, making you feel more lethargic. Lethargy may also lead to other not so good habits such as snacking during the day, indulging in stimulants, staying up late and so on. This eventually causes resentment.
2. The second reason involves the fact that programming is **highly cognitively intensive and stressful job**, and the **mental fatigue **can take its toll.
3. Third, it may be that you are burned out because the work you are doing is, in fact, soul-sucking and unrewarding. The only solution to that would be to take **time off and do some soul-searching** on what you would like to work on without thinking of money as a factor.
4. I didn’t come up with the fourth reason myself and instead found it in the [Hacker News comments section]( /read_rLzQxtb) while doing research for this article. One guy accurately described that _“burnout is caused when you repeatedly make large amounts of sacrifice and or effort into high-risk problems that fail. It’s the result of a negative prediction error in the nucleus accumbens. You effectively condition your brain to associate work with failure.”. _This rings so true to me. Not a day goes by without failures when creating software.
I have dealt with burnout a couple times myself. None of these times made me quit programming for good, or even for as long as a month, but at the very least it made me doubt if
These articles act as an evidence that burnout is a real and common phenomenon in IT industry. Having dealt with burnout myself, I wanted to explore this issue deeper and help others deal with it or even prevent it in the first place.
### Why burnout happens
Burnout seems to occur amongst the programmers more often than professionals in other fields. I don’t have a definite answer as to why this happens, but I suspect there are four main reasons.
1. The first one is **physical**. Sitting at your desk, in front of the computer every day, is unhealthy, making you feel more lethargic. Lethargy may also lead to other not so good habits such as snacking during the day, indulging in stimulants, staying up late and so on. This eventually causes resentment.
2. The second reason involves the fact that programming is **highly cognitively intensive and stressful job**, and the **mental fatigue **can take its toll.
3. Third, it may be that you are burned out because the work you are doing is, in fact, soul-sucking and unrewarding. The only solution to that would be to take **time off and do some soul-searching** on what you would like to work on without thinking of money as a factor.
4. I didn’t come up with the fourth reason myself and instead found it in the [Hacker News comments section]( /read_rLzQxtb) while doing research for this article. One guy accurately described that _“burnout is caused when you repeatedly make large amounts of sacrifice and or effort into high-risk problems that fail. It’s the result of a negative prediction error in the nucleus accumbens. You effectively condition your brain to associate work with failure.”. _This rings so true to me. Not a day goes by without failures when creating software.
I have dealt with burnout a couple times myself. None of these times made me quit programming for good, or even for as long as a month, but at the very least it made me doubt if
Forwarded from URL Reader
I chose the right profession. Since then I have become more strategic about the way I work in order to stay motivated and productive over long-term. In this article I’ll describe the habits I have developed, and techniques I found to be effective to postpone or even eliminate burnout whatsoever.
Some tips and techniques are basic and apply to all people, and while reading them, you will be saying to yourself “D’oh.”. Others are more specific to programmers.
### Let’s start with basics.
1. **Eat well**. Don’t think you need to become a Vegan to feel well. Start with small steps such as drinking water over soda; incorporate more slow carbohydrates and vegetables into the diet; eat regularly and do not overeat. These are the basics that will get you a long way.
2. **Sleep well**. That includes getting good quality sleep and enough of it. There are many things you can do to [create a better sleep environment]( /read_1DhxwUm) and wake up more refreshed. One tip specific to programmers in regards to sleep is to reduce blue-light exposure which may keep you up at night. This can be done by installing [Flux]( /read_Ro2lxJb), which makes the color of your computer’s display adapt to the time of day.
3. **Do not overwork**. It has been shown time and time again that productivity, which, in this case, refers to output, decreases sharply after 4 hours of focused work. It’s impossible to stay productive at a highly cognitively intensive job such as programming long-term, with a long number of working hours every day.
4. **Incorporate **[**Pomodoro technique**]( /read_BxTyQCJ) into your work life. It’s a simple but effective strategy for staying productive as a programmer while at the same getting some necessary break between the tasks. Pomodoro technique involves **25 minutes of focused work, and then 5 minutes of rest**. It works best when you have a specific goal for each Pomodoro. Ideally the breaks will involve activity away from your computer. A brisk walk, some
1 of 3 /more
Some tips and techniques are basic and apply to all people, and while reading them, you will be saying to yourself “D’oh.”. Others are more specific to programmers.
### Let’s start with basics.
1. **Eat well**. Don’t think you need to become a Vegan to feel well. Start with small steps such as drinking water over soda; incorporate more slow carbohydrates and vegetables into the diet; eat regularly and do not overeat. These are the basics that will get you a long way.
2. **Sleep well**. That includes getting good quality sleep and enough of it. There are many things you can do to [create a better sleep environment]( /read_1DhxwUm) and wake up more refreshed. One tip specific to programmers in regards to sleep is to reduce blue-light exposure which may keep you up at night. This can be done by installing [Flux]( /read_Ro2lxJb), which makes the color of your computer’s display adapt to the time of day.
3. **Do not overwork**. It has been shown time and time again that productivity, which, in this case, refers to output, decreases sharply after 4 hours of focused work. It’s impossible to stay productive at a highly cognitively intensive job such as programming long-term, with a long number of working hours every day.
4. **Incorporate **[**Pomodoro technique**]( /read_BxTyQCJ) into your work life. It’s a simple but effective strategy for staying productive as a programmer while at the same getting some necessary break between the tasks. Pomodoro technique involves **25 minutes of focused work, and then 5 minutes of rest**. It works best when you have a specific goal for each Pomodoro. Ideally the breaks will involve activity away from your computer. A brisk walk, some
1 of 3 /more
The JavaScript Ecosystem Demystified
http://blog.differential.com/the-javascript-ecosystem-demystified/
http://blog.differential.com/the-javascript-ecosystem-demystified/
Differential's Blog
The JavaScript Ecosystem Demystified
A crash course for Meteor Developers The JavaScript ecosystem can be a confusing place. With the rapid pace of progress on both the server-side and client-side it can be hard to keep up. And as Meteor developers, we're often sheltered from a lot of this turmoil.…
Forwarded from Kamal
A better model than Wikipedia ?
http://qz.com/480741/this-free-online-encyclopedia-has-achieved-what-wikipedia-can-only-dream-of/
http://qz.com/480741/this-free-online-encyclopedia-has-achieved-what-wikipedia-can-only-dream-of/
Quartz
This free online encyclopedia has achieved what Wikipedia can only dream of
With the right people and a little effort, we could have the internet we always wanted.
N
https://www.packtpub.com/packt/offers/free-learning
Hari ini - BackTrack 5 Wireless Penetration Testing Beginner’s Guide
Utk perbincangan berkaitan software development, boleh join group ni - https://telegram.me/joinchat/ACIF0AHECE1iRuNgLxJicA