Tips I use to avoid burnout
Isn't this obvious to every software engineer I know? Perhaps I am missing something or living under a rock in my own ecosystem. Every single engineer I've ever met knows these things: Don't over commit, take breaks, seek help and know that time is important, may be remember to breathe? I am sorry, but this is not some deep insight.<p>The author works at Google. I presume that if one is getting paid in excess of $200k, you're a damn good professional at the very least. These things need not be reminded or taught - they're <i>required</i> and <i>necessary</i> as a professional software engineer.<p>Burn out happens when - the company or team is under duress, imagine running a manufacturing software system and your factory lines are down. Yes, that gets intense and you can have a burn out if problem requires rehauling the system (takes 6 months say). Or the company is on the brink of collapse and you're one of the 3 engineers holding it together. But, that's not because of the reasons listed here. In fact, writing such an article is dismissive because it distracts the discussion on what <i>really</i> leads to burn out.