The Joy and the Exhaustion: How AI Coding Tools Rewired the Developer Reward Loop

I’m noticing something unsettling in how I’m working, and I keep hearing the same contradiction from other developers: “I’ve never had this much fun coding—and I’ve never been more exhausted.”

The “satisfaction cycle” has collapsed. Before AI coding tools, shipping a meaningful feature took days. The work was measured in weeks of steady effort, then release, then feedback. There was space between the effort and the reward. Now, with Copilot, Claude, and Codex, that distance is minutes. Write a prompt, get working code, iterate, see it run. The feedback loop is immediate. The dopamine hit is real, and it comes every few minutes instead of every few days.

That speed is why the work feels alive again for so many people. It’s also why so many people sound terrified by how much they want to keep going.

I thought about a 1980s anti-drug ad: “I do coke, so I can work longer, so I can make more money, so I can do more coke.” The logic was crude, but the principle stuck: a self-reinforcing loop where the next hit is always a prompt away. You don’t notice it reshaping your behavior until you can’t stop, and by then the shape has already changed.

But here’s what makes me uneasy: I’m not sure the tools are the problem. They’re incredible. The problem might be that the reward loop is so fast now that “this is the most fun I’ve had coding in 20 years” and “I don’t know if I can keep this pace up” can both be true at the same time, and the second part gets quieter while you’re riding the first.

Is this what a builder’s doom-scroll looks like? Not addiction to the tools—addiction to the feedback, to the momentum, to the sense that you’re always one prompt away from the next small win?

The tools aren’t going anywhere. But if you’re feeling this contradiction, the real question isn’t whether to use them. It’s this: How are you keeping the joy of this pace without letting the pace become the point?

---

Originally published on LinkedIn.