loading words...

Feb 26, 2019 23:54:55

Tips for Avoiding Developer Burnout Part 1

by @danielmiller PATRON | 208 words | 10🔥 | 248💌

Daniel Miller

Current day streak: 10🔥
Total posts: 248💌
Total words: 67900 (271 pages 📄)

Burnout is a frequent topic of developer conversations, conference talks, blog posts, etc. Why are so many developers suffering from burnout?

First I think it's important to observe that some people work tons of hours, either on the clock or on their own time, on technology and specifically coding projects without ever burning out. Burn out is not just a factor of how much one is working.

I believe that burnout is more a factor of:

  • Not finding meaning in one's work
  • Being routinely frustrated, for example by working on a feature that is never used by customers or on code that's never merged or otherwise scrapped, an umbrella that also includes constantly changing requirements, dealing with infuriating coworkers and bosses, and company cultures that do not cultivate learning or allowing people to perform at their best.
  • Feeling overwhelmed at the amount of information processing and learning time required to stay up-to-date on current technologies.
  • A long-tail of other demotivating factors.

So it's not just a factor of being overworked, it's a factor of doing the wrong kind of work in the wrong kind of conditions.


Almost broke my streak today, because I was consumed by some work! Barely sneaking this one in on time! Part 2 tomorrow, hopefully. 

From Daniel Miller's collection:

contact: email - twitter / Terms / Privacy