Every developer who relies heavily on AI tools has had this moment: Claude, Copilot, or Cursor has an outage, and the reaction isn't "mildly annoying." It's something closer to genuine disorientation — a few seconds of not quite knowing how to start the thing you were about to do.
Why this specific moment is so revealing
Most days, you can't easily separate "using AI because it's genuinely faster" from "using AI because you've stopped attempting things yourself first." The two look identical from the outside — same code shipped, same velocity. An outage removes the option entirely, for exactly as long as it lasts, which makes it one of the only moments where the gap between the two becomes visible to you in real time.
If the outage is a mild inconvenience — you shift to something else, or work a bit slower on the same task — that's a sign the reliance is more habit than dependency. If it derails the whole session, or triggers something closer to panic than annoyance, that gap between "inconvenient" and "can't function" is worth paying attention to, not brushing off as normal.
It's not really about the outage
The outage itself is rarely the actual problem — most are resolved within an hour or two, and nobody's asking you to work through a multi-day blackout. What it exposes is a baseline you don't normally get to see: what your actual, un-augmented working speed and confidence look like right now, today, not a hypothetical from before you started using AI tools. For a lot of people, that baseline turns out to be rustier than they expected.
Turning an outage into useful information instead of just stress
Next time it happens, instead of just waiting it out irritably: notice specifically what you reach for first when the tool isn't there. Do you open documentation? Try to remember the syntax? Or do you mostly just sit stuck, unsure how to proceed without a chat window? That specific reaction — not the general feeling of "this is annoying" — is the actual diagnostic. It tells you which skill quietly went soft, which is more useful than the vague sense that something has.
Outages are involuntary and rare. You can run the same experiment on purpose, on your own schedule, without waiting for an incident — that's most of what a deliberate practice session is.
See how you'd score on this specifically — it's question 3 on the actual test →
Related reading: AI Coding Addiction Symptoms · How to Quit Vibe Coding