Avoiding Developer Burnout: Practical Habits
Burnout is a pattern, not a personal failing. Learn the warning signs, the causes specific to software work, and the habits that help.
By Velloreth
What burnout is
Burnout has three components, and all three are usually present:
- Exhaustion — tiredness that rest does not fix
- Cynicism — detachment from the work, the users or the team
- Reduced efficacy — a feeling that nothing you do matters
It is a response to a work pattern, not a personal weakness. The World Health Organization classifies it as an occupational phenomenon rather than a medical condition, which is the useful framing: the cause is in the work.
The causes in software
Unclear scope that keeps changing. You build something, the requirement changes, and the work is discarded. The effort is real and the progress is not.
Constant interruption. A developer needs a long block to work on a hard problem. A day of meetings and messages in fifteen-minute gaps produces no deep work, and the feeling of a wasted day.
A long project with no visible progress. A six-month project has no finished work for five months, which erodes the sense of efficacy.
An on-call rotation with no recovery. A night of pages followed by a normal workday is a debt that accumulates.
A mismatch between effort and recognition. The work is hard and nobody notices.
A lack of autonomy. Being told how to do the work as well as what to do removes the part that is satisfying.
The warning signs
Behavioural:
- Procrastinating on tasks you used to enjoy
- Irritability in a code review
- A drop in your own quality that you notice and cannot correct
- Dreading the start of the day
- Working late to avoid a task rather than to finish one
Cognitive:
- Difficulty concentrating on a problem you could once hold in your head
- A feeling that the work is pointless
- Cynicism about the users or the product
Physical:
- Sleep that does not restore
- Headaches, or a change in appetite
The early signs are the ones to act on. A pattern that is caught early is a pattern that can be changed.
The habits that help
Protect a block of deep work. Two hours with no messages is worth more than a day of fragmented time. Put it in the calendar and treat it as a meeting.
Finish something small. A finished task restores the sense of progress that a long project erodes. Break the project into pieces that can be completed and shown.
Make the work visible. A board, a changelog or a weekly note shows progress that is otherwise invisible.
Reduce the work in progress. Three tasks in progress and none finished is a recipe for the feeling of no progress. One at a time.
Take the recovery after on-call. A rotation that does not allow it is a rotation that will burn the team.
Say no to a scope change, or renegotiate it. A change is fine if something else is dropped. A change that is added is a change that costs the team.
Separate the identity from the work. A bug in your code is not a defect in you. This is easier to say than to do, and it is the belief that makes a review painful.
Use the time off. A holiday with a laptop is not a holiday.
Talking to a manager
Describe the work pattern, not the feeling.
Weak: "I'm feeling really burnt out."
Strong: "The scope has changed every week for a month, and the
on-call rotation has no recovery day. I can't hold a
deep-work block, and my output has dropped."
A concrete cause is something a manager can act on. A general statement of exhaustion invites sympathy and no change.
Propose a change. “I’d like to move the standup to the afternoon so the morning is uninterrupted” is a request that can be granted.
Escalate if nothing changes. A pattern that persists after a conversation is a pattern that will not change on its own.
What does not help
Working more hours. It treats the symptom and deepens the cause.
A holiday as the only fix. It helps a tired developer and does not fix a broken process.
Waiting for the project to end. The next project has the same pattern.
Comparing yourself to someone who seems fine. You see their output and not their hours or their support.
Treating it as a discipline problem. The cause is in the work, and the fix is in the work.
A quotable summary
Burnout has three components: exhaustion, cynicism and a reduced sense of efficacy, and it is a response to a work pattern rather than a personal weakness. The common causes in software are unclear scope, constant interruption, a long project with no visible progress, and an on-call rotation with no recovery. The habits that help are a protected block of deep work, finishing something small, reducing work in progress, and describing the work pattern to a manager rather than the feeling.
Related reading
For the focus side, see deep-work-for-programmers and for the planning, estimating-software-tasks. For the broader context, remote-work-communication and technical-debt-conversation.