You know the feeling. You close your laptop at 6:01 PM, and the thought of opening it again—even for that side project you were so excited about last month—makes your stomach tighten. You tell yourself you’re just tired. Maybe you need a vacation. Maybe you’ve lost your passion.
But the truth is crueler. You haven’t lost your passion. Your job has stolen the play.
That Hacker News thread from a developer who’d been coding for 20 years said it perfectly: “After a day of dealing with issue trackers, AI-generated accessibility reports and all that crap, I find it harder and harder to switch to my side projects.” He’s been logged out of his personal projects for months. Sound familiar?
This isn’t burnout. Not really. Burnout is a personal failure story that lets companies off the hook. The real story is structural: modern software engineering has quietly transformed from a creative craft into a bureaucratic curation machine.
Think about what your day actually looks like. You’re not building things. You’re navigating tickets, updating Jira, wrestling with CI/CD pipelines, generating compliance reports, reviewing AI-written code comments, and attending meetings where you explain why your code works. The actual coding—the moment where you lose yourself in the flow—has been squeezed into a shrinking corner of your calendar.
When every keystroke is tracked, estimated, and accountable, the magic evaporates.
We used to code because it was a playground. A place where you could build something from nothing, laugh at your own bugs, and feel that rush when a stupid idea actually worked. But now the playground has been paved over with a parking lot of process. The very act that once made you feel capable, curious, and alive is now bound to obligation and performance.
And here’s the twist: the more your identity depends on coding as work, the less it can serve as an escape from work. Your side project feels like overtime because your job has already colonized that part of your brain. You’re not avoiding the hobby—you’re avoiding the feeling of being evaluated.
I’ve seen this firsthand. A friend of mine, a brilliant backend engineer, spent weekends building a game engine for fun. Then his company announced a hackathon with prizes. He entered, won, and suddenly his hobby was a deliverable. He hasn’t touched the engine since. The moment play becomes performance, it dies.
So what do you do? Quit? Force yourself to code anyway? Neither works. The real solution is to acknowledge that the problem isn’t you—it’s the institutionalization of creativity. You need to reclaim coding as a genuinely pointless act. No goals. No trackers. No audience. Write a script that draws a cat in ASCII art. Make a to-do list app that only you will ever use. Or don’t code at all. Pick up a guitar. Bake bread. The point is to separate the joy from the obligation.
Maybe the most rebellious thing you can do as a developer is to code for no one but yourself—and to let yourself enjoy it again.
And if you never open that side project again? That’s fine too. The original spark of curiosity that made you love coding isn’t gone. It’s just buried under a pile of Jira tickets. You can find it again—but only if you stop treating your hobby like a second job.
FAQ
Q: Isn't this just burnout? Can't you just take a break?
A: Burnout is a symptom, not the cause. The cause is the structural mismatch between the craft you love and the job you're doing. A break helps temporarily, but unless you address the underlying institutionalization of your work, you'll end up in the same place.
Q: What should I do if I can't bring myself to code after hours?
A: Stop feeling guilty. Instead, reclaim your hobby by doing it without any metrics, goals, or deadlines. Write a stupid script, make a game for yourself, or just don't code at all. The point is to separate the joy from the obligation. If you never open that side project again, that's okay.
Q: Some people say you should just do side projects for money to stay motivated. Isn't that a good idea?
A: That's exactly the problem—turning your hobby into another job. The moment you monetize a side project, you've re-institutionalized it. The real answer is to code for play, not for profit. Let go of the idea that every line of code must be productive.