The Discipline of Rest

I want to say upfront that I'm not a therapist, a psychiatrist, or any kind of mental health professional, and nothing here is meant to stand in for actual clinical care — if you're struggling, a qualified professional is genuinely the right place to start, not a blog post from a software engineer. What I can offer instead is something narrower and more personal: what burnout actually felt like from the inside, and what slowly, imperfectly, helped.

The version of burnout I experienced didn't arrive as a dramatic collapse. It arrived as a kind of flattening. Things that used to interest me stopped interesting me. I could still do the work — in fact I was, by every visible metric, performing fine — but the part of me that used to feel curious about a hard problem had gone quiet, and I didn't notice it was gone until someone else pointed out that I hadn't seemed excited about anything in months. That's the part I think doesn't get talked about enough. Burnout is not always exhaustion you can feel in your body. Sometimes it's a much subtler erosion of the part of you that wants things.

For a long time I treated rest as a reward I had to earn through sufficient output, which meant I never actually rested — I just stopped working while remaining fully occupied by the mental tally of everything I should have been doing instead. That's not rest. I've come to think of that as one of the more common traps for people whose identity is heavily tied to being productive: you learn to simulate rest without ever actually getting its benefit, because some part of your mind treats stillness itself as a debt being accrued.

What actually started to shift things, slowly, was much less dramatic than I expected. It wasn't a retreat or a big lifestyle overhaul. It was learning to notice, honestly, the difference between being tired and being depleted. Tired responds to sleep. Depleted doesn't — you can sleep eight hours and wake up just as flat as when you went to bed, because what's worn down isn't your body's energy reserves, it's something more like your capacity to care about things, and that recovers on a completely different timeline, one that doesn't respond to willpower or a better morning routine.

I also had to unlearn a belief I'd absorbed without ever examining it: that needing rest was a kind of weakness, evidence that I couldn't handle what people who were "built for this" could handle easily. I don't think that belief is true, but I understand exactly where it comes from — a culture, both in tech and more broadly, that treats visible tirelessness as a virtue. I've watched that belief break people I respected far more than it ever built anyone up.

The thing that helped most, in the end, was embarrassingly simple: talking about it honestly with people I trusted, instead of performing fine. Not a grand confession, just small, ordinary honesty — telling a colleague "I'm running on empty this week" instead of quietly overcompensating. Every time I did that, I expected some kind of judgment and instead got something closer to recognition. It turns out a huge number of people carrying the same flatness are also carrying it silently, each one assuming they're the only one.

I still don't think I've fully solved this — I don't think it's the kind of thing that gets "solved" once and stays solved. It's more like a maintenance practice, the same way a system needs ongoing care rather than a single fix. What I try to hold onto now is a simple test: am I resting because I've decided rest has value on its own, or am I resting because I've run out of the ability to keep going? Those look similar from the outside. They are not the same thing, and only one of them actually restores anything.

If you recognize any of this in yourself, I'd say the same thing I wish someone had said to me sooner: it's worth talking to an actual professional, not just working through it alone by reading things like this. This is one person's experience, offered honestly, and not a substitute for real care.