🔥 Claude Code Is (Seriously) Burning Me Out

Source: Dev.to

Claude Gave Me a Productivity Problem

I’m more productive than I’ve ever been in my life, full stop. I’m also more burned out than I’ve ever been in my life, full stop. Those two things are not a coincidence. That’s the whole point of this article. Here’s what actually happens when Claude Code starts working for you: You ship something fast. Like, embarrassingly fast. You see results. You see what’s NEXT. You build that too. You see what’s next after that. You build that too. Ship fast → see results fast → see MORE to build → say yes to all of it → repeat. 📊 See the diagram on alextong.me → It’s not a bug. It’s the design. Faster feedback loops make the backlog feel shrinkable. The backlog is never shrinkable. It’s infinite. You just have a better view of it now. I call it the Catch-22 of AI productivity. Claude Code doesn’t give you more time. It gives you more visibility into everything you could build. And the gap between “what exists” and “what’s possible” is bottomless. Let me be specific, because vague burnout talk is useless. In the last few months I have: Fully shipped Count Tongula’s Eye Break — my free macOS app that enforces the 20-20-20 rule (Eye health is so important!) Completely rebuilt my personal portfolio website from scratch Setup my first OpenClaw Started creating my own soda Completely rebuilt 7 web development portfolio projects from half a decade ago Finished producing my next dance track — drops April 3rd That’s not a side project list. That’s a whole creative life that Claude Code made feel simultaneously possible. Every single one of those things felt easy-ish. Low activation energy. Just spin up a session and go. That’s the trap. When everything feels small and easy, you say yes to everything. And then you wake up and you’re maintaining five projects, you have a 40-hour day job, and you haven’t slept more than 4-5 hours a night in two weeks. Steve Yegge — former engineer at Google and Amazon — wrote about what he called “sleep attacks.” After long Claude Code sessions, he’d randomly fall asleep mid-day without warning. His colleagues were talking about installing nap pods. A Harvard Business Review study tracked workers at a 200-person tech company for eight months. AI didn’t reduce their work. It made them work faster, take on more tasks, and extend into more hours of the day — without being asked to. They specifically flagged “fatigue, burnout, and a growing sense that work is harder to step away from.” Bloomberg literally published a piece this month calling it “The Great Productivity Panic of 2026.” Vibe coding was supposed to be chill. The vibes are clearly off. Every burnout article tells you to take breaks, log off at 6pm, go touch grass. Cool. Not the answer. The real answer: put friction back in the process. Because Claude Code removed all of it. I actually ran this problem through five different expert perspectives — behavioral psychologist, stoic philosopher, systems designer, burnout researcher, real developers. All five landed in the same place. Not “do less.” Something more specific: Rule 1: Work in 2-week sprints. Ship something. Then don’t touch anything new for 3 days. That’s it. When you ship — anything — you’re locked out of starting new implementation work for 3 days. You can plan, document, think. No coding. No new sessions. No “just one quick thing.” Before AI, shipping felt like an ending because you were exhausted. You needed the break naturally. Now shipping feels like a green light — you close one terminal and open another. The 3-day lockout puts the ending back in artificially. Rule 2: On top of that I also built a Kanban board in Notion. Hard rule — only 3 projects in “active” at any given time. Want to add something new? Something else has to move out first. The Kanban tells me what I’m working on. The lockout tells me when to stop. Claude Code can’t make either of those calls. That’s the whole point. Claude Code didn’t make me a more productive engineer. It made me a person who ships software, produces music, builds apps, brews soda — things I never in my life thought I would have the time or resources for. That’s genuinely incredible. I don’t want to give that back. But the expansion of what’s possible is not the same as having more capacity. Your bandwidth as a human didn’t 10x. Your output ceiling did. That gap — between what you can see and what you can actually sustain — that’s where burnout lives. The answer isn’t to slow the tool down. It’s to be more deliberate about what you point it at. Three projects, three day breaks. Hard limit. Everything else waits. How are you managing this? Drop your approach in the comments — genuinely curious what’s working for other people. Update: Anthropic’s session limits accidentally became part of my fix — more here →. I’ve been a software engineer for more than half a decade, previously at Amazon and The New York Times. These are observations from the trenches — not predictions.