Burnout is what happens when stress at work goes on for too long without enough recovery, until even ordinary tasks feel heavy. It isn't laziness or a lack of passion, and it rarely announces itself: it tends to creep in while you still look busy and productive.
What burnout actually is
The World Health Organization describes burn-out in its International Classification of Diseases (ICD-11) as an occupational phenomenon: the result of chronic workplace stress that has not been successfully managed. It is listed as something that affects health, not as a medical condition in its own right. The WHO names three dimensions:
- Exhaustion: feeling drained, with no energy left for work or anything else.
- Mental distance from the job: cynicism, negativity, or not caring about work you used to enjoy.
- Reduced effectiveness: feeling that you get less done, and do it less well, however hard you try.
The important word is 'chronic'. A hard week before a launch is stress, and most people recover from it with a good weekend. Burnout builds when the hard week never ends: the pressure stays on, and the rest that would normally undo it never arrives. Stress on its own isn't the problem. Stress with no recovery is.
Why developers are prone to it
Nothing about software makes burnout inevitable, but a few things about the work make it easy to slide into.
- The work never runs out. There is always one more ticket, one more bug, one more review. Nothing tells you when you are done for the day.
- You are always reachable. Team chat, on-call rotas and deploy alerts follow you home, and a message at 10pm feels like it needs an answer.
- The tools never stop. A laptop, a terminal and an AI coding assistant make it possible to keep fixing 'one more thing' at 3am. Being able to keep going isn't a reason to.
Wondering how this was made? How we make these