Quentin Rousseau has started going to bed before his laptop does. For months, he couldn't. A developer and blogger, Rousseau spent the better part of last year losing hours to Claude Code — not to finish anything specific, but because stopping felt impossible. "Prompts were composing themselves behind my eyelids," he wrote in an essay published March 9. "The mental terminal was still running after the laptop closed."
Eventually, he saw a doctor. He was prescribed an orexin-receptor antagonist — a drug that chemically suppresses the wakefulness signals his brain had locked into 'on.' He's writing about it now because he doesn't think he's unusual.
The essay makes a straightforward case: agentic AI coding tools operate on the same reward architecture as slot machines. The unpredictable swing between a clean working build and a spectacular agent failure — variable ratio reinforcement, in behavioral psychology terms — generates a compulsive loop that's genuinely hard to break by willpower alone. That's not a character flaw. It's the mechanism.
He's not disputing the productivity gains. They're real, and loudly documented. Garry Tan, CEO of Y Combinator, posts about Claude Code the way people used to post about espresso — a dependency you develop and eventually stop being embarrassed about. Tan has described sessions stretching to 5 AM on X, using the word "addicted" with an energy that reads more as pride than as warning. Around a quarter of companies in recent YC batches have codebases that are almost entirely AI-generated, a figure Tan has cited as evidence of a new kind of founder capability.
Rousseau's concern isn't the company metrics. It's that nobody seems to be asking what it's costing the people underneath them.
Steve Yegge's recent essay "The Brute Squad" runs in a similar vein. Yegge — who has been writing about programming culture for two decades — described a nightly ritual of physically sprinting from his computer and jamming fingers in his ears to resist the pull of one more prompt. He frames it as an environmental hazard to be managed, not a personality quirk to be proud of.
What Rousseau identifies as genuinely new is the structure of the compulsion. Traditional workaholism at least had friction — you had to open something, load something, drag yourself back into the work. Agentic coding collapses that. You hand off a task and watch it run; the passive engagement of the spectator effect keeps you present without requiring active effort, which means the cognitive ceiling that eventually forces people to stop simply doesn't engage. Infinite task branching does the rest: every completed feature surfaces three more, eliminating the natural sense of closure that might otherwise signal an end point. Layer on a professional culture that treats shipping velocity as a proxy for personal worth, and you have something the industry hasn't seriously examined.
"We learned — painfully, over decades — that crunch culture in game development destroys people," Rousseau writes. "We're watching the same dynamic emerge with AI coding, except this time the crunch is self-inflicted and disguised as fun."
He doesn't offer a fix. He mostly wants people to stop treating the symptom as a status signal. When a colleague mentions they coded through the night, he suggests, the right response probably isn't congratulations.