I was scrolling through Twitter (I will always call it Twitter...) the other day and I saw it again. Another developer posting about hitting their rate limit mid-flow. The panic. The frustration. The "no no no, not NOW" reaction. Then a service outage hits and my WhatsApp groups light up. Slack communities go into meltdown. Everywhere I look, developers are talking about that moment when their AI coding assistant goes silent and they realize they don't know what they are going to do next. Rate limits, outages, degraded performance. Doesn't matter what causes it. The reaction is the same.
That reaction? It looks a lot like addiction. Maybe not the clinical kind but rather that kind where a tool becomes so embedded in your workflow, that removing it feels impossible. And if you've been using AI coding tools for any length of time, you've probably seen it in yourself too.
The Numbers Tell a Story
Let's start with what's happening at scale. 84-90% of developers are now using AI coding tools. 51% use them daily. Claude Code grew 80x in a single year, far exceeding Anthropic's planned 10x. Cursor went from zero to $2 billion ARR in three years. Uber burned through its entire 2026 AI budget by April because Claude Code spread across 5,000 engineers faster than anyone anticipated. These are not the adoption curves of a "nice to have" productivity tool. This is deep integration. This is dependency at an organizational level.
