I used to think I occasionally suffered from work burnout, but then my SO became a medical resident, and I realized "oh, that's what burnout is."<p>What I used to "suffer" as a programmer was the ebb and flow of productivity. As described by books like "Drive" and "Flow". This state-of-mind was perhaps best described for me by my colleague (also a programmer) in this public essay, "Find the right routine to surf productivity"[1].<p>What my SO suffers as a medical resident is <i>true</i> work burnout. They work 6 days per week, nearly 80 hours per week, for weeks (or months) on end. Their work is not only challenging intellectually, it's challenging physically and emotionally. Their work also buckles under the weight of administrative bureaucracy, which removes their sense of agency.<p>Recently, after my SO got off a 5-week "night float" block (where she worked 6 days per week on an inverted 6pm-6am night-time schedule), she finally got a day off. It was really a day to re-adjust her schedule back to working "normal" daytime 6am-6pm hours. During that day, she said to me, "Can we look up Maslow's hierarchy of needs?"[2]<p>Looking over that diagram, we realized her work had her floating around in the first couple levels of that pyramid, whereas in my work, I was very much at the top. My "burnout" feelings were really "not feeling perfectly self-actualized". Her "burnout" feelings were actually "not having access to basic physical needs (e.g. sleep) and emotional support (e.g. daylight, friends, family)."<p>I am very much in favor of Jason Fried style "Calm Companies"[3], and I think in software/tech, we actually have the ability to "work hard" without burning out, usually hovering around the "self-actualization" level in the pyramid. One of the wonderful things about software engineering, in particular, is that since it is the art of automation, we can actually save ourselves labor, and think carefully about the notion of employee leverage. That is, one employee's code can do the labor of hundreds or thousands.<p>It's really sad to me that the medical profession, at least during its training period for new medical school graduates, there is an epic contrast: the near-guarantee of burnout, with basically no recourse for residents except to "suck it up and power through".<p>For those of you who feel your are in jobs in tech where managers "put the screws on you", you should recognize that you have all the power in the world to change job. Employers in tech should be fighting over you, ensuring you feel fulfilled, productive, <i>and</i> balanced. "All of the above" is possible; this isn't a "pick two" engineering trade-off. If you don't feel that way, it's bad management or bad culture -- period. In medical residency, it's "pick zero", and even worse, there is no way for those folks to change jobs (at least, not without derailing their entire career).<p>[1]: <a href="http://lifehacker.com/5955115/find-the-right-routine-to-surf-productivity" rel="nofollow">http://lifehacker.com/5955115/find-the-right-routine-to-surf...</a><p>[2]: <a href="http://timvandevall.com/wp-content/uploads/2013/11/Maslows-Hierarchy-of-Needs.jpg" rel="nofollow">http://timvandevall.com/wp-content/uploads/2013/11/Maslows-H...</a><p>[3]: <a href="https://m.signalvnoise.com/the-calm-company-our-next-book-d0ed917cc457" rel="nofollow">https://m.signalvnoise.com/the-calm-company-our-next-book-d0...</a>