I didn't realize I was burned out until I couldn't force myself to open my laptop on a Monday morning. Not "don't want to." Couldn't. The thought of writing another line of code filled me with something between dread and complete indifference. That's when I knew something was seriously wrong.

How It Started

It crept up slowly, which is why I didn't catch it. I was working full time, maintaining two side projects, learning Web3 on weekends, and writing blog posts about all of it. For about eight months, I was coding 10-12 hours a day, six or seven days a week. I told myself I was being productive. I was "building my skills." I was "staying ahead."

The first sign was losing interest in side projects. Things I'd been excited about felt like obligations. Then the day job started feeling the same way. Code reviews that used to be interesting became tedious. New feature requests triggered irritation instead of curiosity. I started dreading standup meetings.

I also stopped learning. I'd open a technical article, read two paragraphs, and close the tab. My attention span collapsed. I couldn't focus on anything complex for more than 20 minutes. I was constantly tired but couldn't sleep well. Classic burnout symptoms, but I didn't recognize them at the time because I'd never experienced it before.

The Break

I took three weeks off. Not a vacation where I coded from a different location. A real break. I closed my laptop and didn't open it. Didn't check GitHub. Didn't read Hacker News. Didn't think about code.

The first week was uncomfortable. I felt guilty for not being productive. My identity was so wrapped up in being a developer that not coding felt like not being myself. I kept reaching for my phone to check work Slack, then catching myself.

The second week was better. I read fiction for the first time in months. Went for long walks. Cooked actual meals instead of ordering food. Spent time with friends talking about things that had nothing to do with technology. It sounds simple, and it is, but I'd completely stopped doing all of it.

By the third week, something interesting happened. I started getting ideas again. Not because I was trying to, but because my brain had space to think about things that weren't task lists and sprint backlogs. I found myself curious about a technical problem and for the first time in months, the curiosity felt genuine instead of forced.

What I Changed

Coming back, I made some rules for myself that I've stuck to since.

No coding after 7pm on weekdays. The laptop closes. Whatever I was working on can wait until tomorrow. This was the hardest rule to enforce because "just one more thing" is the developer's eternal trap. But the boundary matters. My brain needs time to decompress, and that doesn't happen if I'm staring at code until midnight.

One side project maximum. I used to have three or four going at once. Now I pick one, work on it until it's done or I deliberately decide to stop, and only then start something new. The context switching between multiple projects was draining me without producing anything meaningful.

Weekends are optional. If I feel like coding on Saturday, great. If I don't, that's also fine. The moment coding on weekends becomes an obligation instead of a choice, I know I'm heading toward burnout again.

Physical activity is non-negotiable. I started running three times a week. I'm not fast, I'm not training for anything. But getting out of the chair and moving my body does something for my mental state that no amount of "productivity optimization" can match. On days I run, I'm noticeably more focused and less irritable.

Social time that isn't tech talk. I love talking about technology with other developers. But I was doing it so exclusively that I'd lost touch with other parts of my personality. Now I make time for friends who don't work in tech. Conversations about books, travel, food, whatever. It sounds trivial, but having a life outside of code is what makes the code sustainable.

What I Wish I'd Known

Burnout isn't a sign of weakness. It's a predictable outcome of sustained overwork without adequate recovery. Athletes understand this intuitively. Training without rest leads to injury. The same is true for cognitive work, but our industry glorifies overwork instead of recovery.

The "hustle culture" messaging in tech is harmful. The 10x developer myth. The idea that you should be coding every waking hour. The celebration of all-nighters and weekend sprints. All of it makes burnout seem like a personal failure when it's actually a systemic problem.

If you're reading this and recognizing the symptoms, take the break. Not next month. Now. The code will be there when you get back. Your health and your relationship with your craft are more important than any sprint deadline.

I came back from burnout a better developer. Not because of the break itself, but because I came back with a sustainable pace and clearer priorities. I write less code now than I did before. But the code I write is better, and I actually enjoy writing it. That matters more than velocity.