Burnout and a Sustainable Software Career
Across 13 years in software, I came close to burnout twice. Early signals, practical ways to draw boundaries, the truth that recovery isn't a vacation — honestly.
The first years in software are loved. New things to learn, problems to solve, technology shifting under your feet — exciting. After 5 years, 8 years, 10 years, the same dynamic stops giving you the same reward. Some teams turn against you at this stage; some teams pass right by. The result is the same: burnout.
I've come near burnout twice in 13 years. The first time I didn't see it coming and almost left the industry. The second time I caught it and recovered. The difference is the things you learn between.
This post is honest about a side of the industry that still doesn't get enough air.
What burnout is and isn't
Isn't: a tired week, one bad project, temporary motivation dip.
Burnout is chronic exhaustion. Three dimensions:
- Exhaustion: no energy; weekend sleep doesn't help.
- Cynicism: distance from your work, your team, possibly the industry. "What's the point?"
- Reduced efficacy: feeling unable to do what you used to do well.
If all three are present: burnout. If one is: pay attention.
Early signals
Typical signals, roughly in order:
- Monday mornings are physically hard (not from drinking — just no energy)
- Work topics invade personal time (eating, in bed, you're thinking about a bug)
- Small things become disproportionately annoying (a Slack ping, a bug, a review comment)
- Learning new things has become hard — you used to enjoy it
- It feels more natural to complain than to build
- Weekends don't restore — time just passes
Two or three of these for a month: pay attention.
Causes
Burnout causes are usually accumulated, not sudden. The five most common:
1. Sustained overload. Sprints are full, the backlog is full, the manager keeps adding "and this." Six months later, collapse.
2. Lack of control. You're not part of important decisions, just executing. Years pass like this and motivation erodes.
3. Lack of recognition. The work you do is invisible; rewards don't track seniority.
4. Value conflict. What the company is doing clashes with what you care about.
5. Lack of community. Your team relationships are surface-level; you don't have anyone to vent to.
If 2–3 of those resonate, you're at risk.
Drawing boundaries
The fastest cure to burnout: boundaries.
A defined end of the workday. After hours, close Slack. "Urgent" needs to be genuinely urgent — phone calls, not just email.
Vacation = real vacation. A week off = a week not opening the laptop. No "just one quick check." No Slack glance. No mail. Vacation doesn't pull you out of burnout, but constant availability puts you in it.
Saying "no." A new piece of work arrives but your list is full. "I can't take this on right now; X has to finish before Y starts" is a feature, not a flaw. If you're senior, you should already do this. If you're junior, start practicing.
On-call accepted vs. encroaching. On-call is a duty during the week of rotation. Outside it, being unreachable is your right.
When fatigue won't lift — recovery
You drew boundaries but you're still depleted. Recovery is required.
A vacation isn't enough. A 2-week vacation can't undo 6 months of burnout. Recovery time is what's needed — sabbatical, role change, reduced scope.
Active rest. Not lying in bed — physical activity, nature, hobbies, social. The brain needs to leave "work-think" mode. Reaching that mode takes weeks (2–4).
Phased return. Coming back at full speed after a month of recovery throws away that recovery within 2 weeks. Start at half capacity, ramp gradually.
Sustainable career practices
To not just recover but to never get there:
A marathon, not sprints. A 13-year career can't be run at sprint pace for 13 years. Annual cadence — some years are intense, some are calm. Both are valuable.
Variety. Doing one thing for five years exhausts. Periodically rotate: new tech, new role, new product, new team. Even if the work is similar, the environment shift restores.
Community. Professional friend networks (Slack/Discord communities, local meetups). People to talk to outside your team. The place where you can ask "is this season hard, or is it me?"
Financial floor. A 1–3 year cash reserve. The day you should be able to walk away from a company, your option to leave should be real.
Plan the time off. Two weeks once a year. Or a week every six months. Time off isn't a luxury, it's a career investment.
Tell the company
If burnout is something the company creates (often the case), the company has to know. Talk straight with your manager:
- The load is too much
- I want to drop X responsibility
- A 2-week vacation isn't enough; I'm thinking about a 1-month sabbatical
- I want to switch into Y role
A good company listens. A bad one doesn't — that's the time to leave. Don't hold your health under a company's word.
Closing
The biggest lesson from 13 years: sustainability matters more than speed. The person sprinting and burning out in 5 years achieves less than the steady person doing 15 years. Total impact is decided by sustainability.
Learning this early is a luxury. Most of us learn it the hard way; some by hearing others. I learned it both ways.
If you're tired right now and not getting better, you're not alone. It's very common. Ask for help, accept it, draw boundaries. The good career is the healthy person's career.
Long-form notes on distributed systems, production stability, AI-assisted shipping. No spam, easy to unsubscribe.
Comments
No comments yet. Be the first.