My list would be more like -- How to Burn Out Programming: 1) Do it too much for too long while being under stress. The same way you burn out doing anything.

My list would be more like -- How to Burn Out Programming: 1) Do it too much for too long while being under stress. The same way you burn out doing anything. 2) See #1 I do agree with some of the points laid out in the post, but disagree with #2 and #4. #2 ("Have a negative attitude toward everything") is a bad thing for team morale and should be avoided but I don't believe it has anything to do with burnout. #4 ("Switch jobs often") assumes a very idealized world. The vast majority of jobs are nothing like PhD programs and you have very little freedom to dig deep into a problem unless the problem directly involves revenue generation. I've had to quit a couple of jobs due to the fact that staying there maintaining the same old code base without really expanding functionality or otherwise flexing my "programming muscles" would have been what resulted in my burnout. Part of my issue with this one might be the lack of definition for "often". Obviously if you are switching jobs every 6 months to a year that's not great, but the reality of many modern software companies is that keeping good developers engaged with their job 3-5 or so years in requires very enlightened management, which is rare now. #4 also assumes that as developers it is naturally our goal to become managers and directors. Personally I have zero interest in doing either of those jobs. And I don't think good developers really have to try that hard to prove themselves at new jobs, in my experience it is pretty obvious to other good developers pretty quickly when someone else is good.