There was a week, not long ago, where I got almost nothing done. No commits worth mentioning. No progress on the project I'd been excited about a month earlier. I sat down to work and just... stalled. Every task felt heavier than it should have, and the harder I pushed, the less actually happened.
For a while I called this laziness. It took longer than I'd like to admit to recognize it for what it actually was: burnout, quietly building for months before it finally showed up on a random Tuesday.
Burnout Doesn't Announce Itself
Nobody wakes up one morning and decides to burn out. It creeps in through a hundred small decisions that each seemed reasonable at the time. One more late night to finish a feature. One more weekend spent "just checking in" on something that could have waited. One more year of treating rest as something you earn only after everything is done — which, in this line of work, is never.
The tricky part is that burnout often looks like productivity right up until it doesn't. You can run on adrenaline and habit for a surprisingly long time before your body and mind send the invoice. When mine came due, it didn't show up as dramatic exhaustion. It showed up as an inability to care about things I used to genuinely enjoy. That was the scarier version — not too tired to work, just strangely disconnected from why any of it mattered.
The Instinct to Push Harder
My first response, predictably, was to push harder. More hours. More discipline. Surely if I just tried harder to focus, the fog would lift. It didn't. Pushing harder against burnout is a bit like trying to fix a memory leak by adding more memory — it might buy you a little time, but it doesn't touch the actual problem, and eventually the system falls over anyway.
What actually helped was the opposite of everything my instincts told me to do. I stopped working nights. I stopped treating every evening as an extension of the workday. I let a few things stay unfinished longer than felt comfortable. None of it felt productive in the moment. All of it turned out to be necessary.
Rest Isn't the Reward, It's the Requirement
Somewhere along the way, a lot of us — myself very much included — absorbed the idea that rest is something you earn after the real work is done. Finish the sprint, then rest. Hit the goal, then relax. The problem is that in tech, and honestly in most ambitious work, there's always another sprint, another goal, another thing that could justify pushing rest one more day down the line.
Treating rest as a reward means it never actually arrives, because there's always a reason to defer it. What changed things for me was treating rest as a requirement instead — a non-negotiable part of the system, not a bonus you unlock. Just like a server needs scheduled maintenance regardless of how well it's currently running, a person needs regular rest regardless of how "on top of things" they currently feel.
What Recovery Actually Looked Like
Recovery wasn't dramatic. There was no retreat, no big life overhaul. It was smaller and more boring than that. It looked like actually taking lunch away from my desk. It looked like closing the laptop at a set time instead of "just checking one more thing." It looked like doing something with my hands that had nothing to do with a screen — cooking, walking, anything that gave my brain a break from constant problem-solving mode.
The strange thing is how much these tiny, unglamorous changes did. Within a couple of weeks, the fog that had settled in started to lift. Not because I'd solved some deep existential problem, but because I'd finally stopped running the same loop that caused the fog in the first place.
The Lesson I Wish I'd Learned Sooner
If I could go back and tell myself one thing, it would be this: burnout isn't a sign you need to work harder. It's a sign the current approach is unsustainable, and no amount of willpower fixes an unsustainable system. You can't grind your way out of a problem that grinding caused.
The daily grind is real, and there's genuine value in showing up consistently, in doing the unglamorous work, in pushing through the boring parts. But there's a difference between the grind that builds you up over time and the grind that quietly wears you down until there's nothing left to build with. Learning to tell those two apart, before the invoice comes due, might be the most useful lesson tech ever taught me.