Burnout doesn't look like exhaustion, at first

Everything I’d ever heard about burnout described it as running out of energy, feeling drained, needing more sleep than usual, dreading Monday in a way that gets worse instead of better. So when it actually started happening to me, I missed it for weeks, because none of that showed up first. What showed up first was something quieter and, in hindsight, more useful to know about: things that used to feel good stopped feeling like anything at all.

The ticket that should have felt like a win

There was a specific afternoon I keep coming back to. I’d shipped a fix for a bug that had been quietly annoying users for a couple of weeks, the kind of fix that normally gives you a small, real hit of satisfaction, you close the ticket, maybe mention it in standup, feel briefly good about your day. I closed the ticket, and felt nothing. Not bad, not tired, not stressed. Just nothing, the same flat nothing I’d feel closing a ticket for renaming a config key. I noticed the absence, thought “huh, that’s odd,” and moved straight to the next thing in the queue, which is exactly the problem in hindsight: I registered it as a minor oddity instead of a signal, because I was still waiting for the version of burnout I’d been told to expect, the tired, dragging, can’t-get-out-of-bed version. That version showed up eventually. It showed up roughly six weeks after the flattening did.

Looking back at that stretch, it wasn’t isolated to one ticket. Work that used to have a shape to it, some parts more interesting than others, some wins bigger than others, had gone uniformly gray. Everything took the same amount of effort it always had, I wasn’t visibly struggling to do the work, output didn’t drop in any way a manager would have noticed. What was gone was the variance, the difference between a task that felt good to finish and one that didn’t. Everything just felt like the same effortful nothing, on repeat.

Why “I’m just tired” was the wrong diagnosis

The reason it took so long to name is that I kept reaching for the explanation that matched what I’d been told burnout looks like, and “I’m just tired, I’ll sleep more” was a much easier story to accept than “something about how I relate to this work has changed.” I slept more. It didn’t help, because the problem wasn’t sleep debt, it was that finishing something had stopped meaning anything, and no amount of rest fixes a meaning problem by itself. What actually helped was a conversation with a friend outside the industry entirely, who asked a plain question, “when’s the last time you felt good about finishing something at work,” and I genuinely could not answer it. That gap, not being able to name a recent instance of a feeling that used to happen weekly, was the moment the actual problem got named instead of misdiagnosed as tiredness.

Naming the flattening earlier would have saved weeks

Once it had a name, the actual fixes were fairly ordinary, some time off, a conversation with my manager about workload and about which parts of the job had quietly become obligation instead of choice, and deliberately doing something completely unrelated to code for a stretch. None of that is a novel insight. What I actually want to flag isn’t the fix, it’s the delay. I lost roughly six weeks between the first flattened afternoon and actually addressing it, because I was pattern-matching against exhaustion, the symptom everyone talks about, instead of noticing the earlier and quieter one: satisfaction disappearing from things that used to reliably produce it.

If there’s a single thing worth taking from this, it’s that the checklist most people carry around for burnout, tired, dreading work, can’t sleep, is a late-stage list. By the time those show up, the earlier sign has usually already been running for weeks, uncontested, because it doesn’t look like anything dramatic enough to flag. It just looks like finishing something and feeling nothing about it, which is easy to write off as a one-off bad day, right up until you notice it’s been every day for a month.