What Developer Burnout Actually Felt Like

I Never Thought I'd Come to Hate Code

It was my fourth year. Every morning, the only thought when I opened my eyes was that I didn't want to go to work. Coding — something I used to love — felt like torture. PR reviews piled up and I couldn't bring myself to touch them. During lunch walks, I didn't want to go back. I was anxious on weekends too, because Monday was always just around the corner.

At first I told myself I was just tired. A little rest and it'll pass. But three months later, it hadn't gotten better. It had gotten worse.

How It Started

Looking back, the cause was clear. Three consecutive months of overtime, averaging 60-hour weeks. There were days I'd deploy at 1 AM and be back at my desk by 9 AM. We had to ship new features every week, and technical debt kept piling up. More and more code went to production without tests, and when that code caused incidents, I'd get called in the middle of the night.

On top of that, two key team members quit and my workload jumped by 50%. Telling myself "I should be able to handle this" and "other teams have it worse" was a mistake.

My Body Warned Me First

I had headaches every single day. I kept a bottle of Tylenol in my work bag. On weekends, I heard phantom Slack notification sounds. Even when no alert had actually gone off, I'd think I heard the "ding" and check my phone.

At the worst point, I threw up in the bathroom on a Monday morning. I hadn't eaten anything — my stomach just revolted. That's when I finally admitted: "This isn't normal." Burnout isn't something you overcome through willpower — recovery starts with acknowledgment. It's not weakness. Ignoring your body's signals only makes the price higher.

What I Did

The hardest thing was telling my team lead honestly. "I'm not in a good place right now. Could we adjust my workload for two weeks?" Surprisingly, the response was understanding. "You should have said something sooner." Most managers would rather have someone flag the problem early than have them suddenly quit.

Next, I picked up a hobby completely unrelated to code. I chose running. At first, I couldn't even do 2 kilometers. I'd be gasping after 500 meters. But a month later, after a 5K run, I'd feel my head clear. My brain needed time to focus on something other than code.

I made a rule: no opening my laptop on weekends. At first I was anxious. "What if there's an incident?" But the on-call person handles incidents, and the world doesn't stop if I unplug for 48 hours.

Recovery Took Six Months

There was no quick fix. I adjusted my workload, started exercising, and stopped coding on weekends. Even so, it took six months before coding felt enjoyable again. Recovery is gradual. Then one day, I found myself thinking "Oh, tracking down this bug is actually fun." That's when I knew: "I'm back."

What Changed After Burnout

Now, even when I work overtime, I never exceed twice a week. Slack notifications are off after work hours. The biggest change is that I learned how to say "no." Before, I accepted every request because I was afraid declining would make me look incompetent. Now I can say "It would be more realistic to push this to the next sprint."

Saying no isn't irresponsible. Accepting more than you can handle and letting quality suffer — that's the real irresponsibility.

When a Colleague Is Burning Out

Having been through burnout myself, I can now recognize the signs in teammates. When someone usually lively suddenly goes quiet, when their PR review pace slows dramatically, when they zone out in meetings — I offer them a coffee. A simple "How have you been?" can mean the world to someone who's struggling.

Looking Back

Burnout isn't evidence of weakness — it's evidence that you've been working hard. The point isn't to never experience burnout; it's how you respond when it happens. And the best response is "acknowledge it and rest." Rest is part of the job.