Burnout

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.
• Enjoyment hides the cost. People who love coding say yes to everything, because each extra task feels like fun at first. The tiredness builds up quietly underneath.
• The cost is invisible. Commits, merged pull requests and a green 'online' dot all look like productivity. Fatigue doesn't show up on any dashboard.

How it builds up

There is no single official timeline, but the pattern is familiar to many developers.

Early on, it looks like success

The first bugs feel like puzzles and the first launch is exciting. Saying yes to extra work feels good, and the output is real: lots of commits, quick replies, weekend deploys that go well. Nobody, including you, sees a problem.

Then the effort stops paying off

The hours stay long, but each one produces less. Small tasks take longer. A simple bug that would once have taken ten minutes takes an afternoon. Reading one message feels like a chore.

Finally, normal work feels heavy

You read the same line of code five times and it still doesn't go in. You stare at the screen but can't focus. Work you once enjoyed now brings dread or indifference. This is the point where many people finally notice, and it is later than it needs to be.

The signs to watch for

Burnout shows up in how you think, feel and behave. None of these signs proves burnout on its own, but several together, lasting weeks, are worth taking seriously.

• Focus: rereading the same line, losing track mid-task, simple decisions feeling hard.
• Mood: dreading opening the laptop, cynicism about the project, snapping at teammates.
• Body: poor sleep, constant tiredness that rest doesn't fix, headaches.
• Behaviour: working longer hours to make up for getting less done.

That last one is the trap. When output drops, the natural reaction is to put in more hours, which means less rest, which makes the next day's output worse again.

Why 'push through' makes it worse

Pushing through feels responsible, but it works against you. Tired attention makes more mistakes, and in software a mistake rarely stays small: a rushed fix can introduce a new bug, a missed edge case can mean a rollback, and a sloppy review can let a problem through to production. Each of those creates more work, which creates more pressure to work longer. The way out of that loop isn't more effort. It is recovery.

A worked example

Consider a backend developer on a small team, a few months after a big launch.

The launch goes well, so the follow-up work piles up: urgent fixes, a new feature, a weekend deploy to hit a deadline. She is on the on-call rota, keeps chat notifications on in the evenings and often codes late because it is quiet then. For a while her commit count is the highest on the team.

A couple of months later, code reviews that used to take twenty minutes take an hour. She rereads the same pull request several times. A bug she would once have enjoyed chasing feels impossible. She starts working evenings to catch up, and gets less done each week.

The turning point is noticing the pattern rather than blaming herself. She tells her lead that she is running on empty. Together they agree:

1. She swaps out of the on-call rota for a few weeks.
2. Chat notifications go off after a set time each evening.
3. The new feature's scope is cut, and one piece moves to a teammate.
4. She takes some leave she had been putting off, and actually stops.

None of this is dramatic. What matters is that the workload changes, not only her willingness to cope with it. Recovery takes weeks, not a weekend, but her focus comes back, and the team learns that a high commit count isn't the same thing as a healthy one.

Recovering from burnout

• Step away. Close the laptop and stop work for a real stretch of time. A break where you still check chat on the sofa isn't a break.
• Cover the basics. Sleep, proper meals, water, some time outside and some movement. They sound too simple to matter, but an exhausted brain can't recover without them.
• Talk about the cause. Burnout comes from chronic work stress, so the fix usually has to change the workload too. Tell your manager or team what is going on and what needs to change.
• Give it time. Months of stress rarely unwind in a few days. Expect to recover gradually.
• Get help when it lasts. If exhaustion, low mood or hopelessness go on despite rest, talk to a GP or doctor. Burnout can overlap with anxiety and depression, and those deserve proper care.

Preventing it

• Set a stopping point. Decide when the working day ends, and turn off notifications after it.
• Say 'not now'. Taking on less, or negotiating scope and deadlines, is part of doing the job well.
• Take real breaks. Use your holidays, and take lunch away from the screen.
• Keep on-call fair. Rotate it, and give people time back after a rough night.
• If you lead a team, praise outcomes rather than hours, and notice the person who is always online. Being always online can be a warning sign rather than a strength.

Common mistakes

• Calling it laziness. Burnout often happens to people who cared a lot and pushed hard for a long time.
• Expecting a weekend to fix it. Short rest helps with short stress. Burnout needs a longer recovery and a change in workload.
• Measuring effort instead of output. Hours online and commit counts say nothing about whether the pace is sustainable.
• Waiting until you are empty. The earlier you notice, the easier it is to change course.

Key takeaways

• Burnout comes from stress that lasts too long without enough rest.
• Early on it often looks like high productivity, which is why it is easy to miss.
• Simple tasks feeling hard, poor focus and dread are signs to take seriously.
• Working longer to catch up makes it worse; stepping away and recovering is the fix.
• Lasting recovery needs a change in workload, not only more willpower.