The Dispatch #57 · April 20, 2026
The Confirmation Loop
For engineers who use AI tools daily
You've noticed it. Every task starts to feel like it needs AI. Not because you're dependent — because the muscle for doing it yourself has quietly atrophied.
So you reach for the shortcut. The shortcut works. You reach faster next time. The loop closes.
This week: how the confirmation loop traps engineers, what it's actually costing you, and how to break it before the gap becomes unrecoverable.
The Confirmation Loop — Step by Step
You use AI to solve a problem. It solves it faster than you expected.
Your brain registers this as "I couldn't have done it that fast." Subtle competence doubt creeps in.
Next problem: you reach for AI before even trying. Velocity reinforces the pattern — it's faster, so why wouldn't you?
The small attempts stop. And the small attempts were where the skill actually lived.
Now every task that doesn't use AI feels slow and uncertain. You've recalibrated your baseline for "normal speed."
You're locked in. Not because AI is bad. Because the loop never let you practice.
The Math Nobody Talks About
If you use AI for 60% of your coding tasks, you're deliberately not practicing 40% of your previous skill. That 40% decays. The 60% grows. But that 40% — the debugging, the architecture decisions, the edge cases — that's where senior engineers live. That's where the work feels like yours.
The loop doesn't just slow your skill growth. It actively erodes what you already had.
One Engineer, One Story
"I spent three years using AI for almost everything. When I finally tried to build something without it — a small API for a side project — I couldn't debug a simple 500 error for two days. I used to debug that in twenty minutes. I didn't realize how much I'd lost until I tried to use it."
The gap doesn't announce itself. It hides in the velocity. By the time you notice it, the distance between "with AI" and "without AI" has become significant.
This Week's Challenge
One Intentional AI-Free Task
Not a big project. Not a week off. Just one afternoon where you let yourself be slow on purpose.
Pick something small. A utility script. A refactor you've been putting off. Something where the outcome matters less than the process of getting there.
The discomfort is the point. The feeling slow is the signal that you're rebuilding something.
Resource of the Week
Asking yourself: "Am I still actually a developer?" — that question has a name and a page.
developer-identity.html — for engineers navigating the identity question that the confirmation loop makes worse.
The AI Fatigue Quiz takes 90 seconds and maps which specific skills have drifted furthest from your unaugmented baseline. Find out where you are in the loop.
Take the Quiz →Skill Atrophy
The slow erosion of generative capacity when origination is outsourced to AI.
Attention Residue
Why your brain can't fully switch tasks — and why AI makes it worse.
Productivity Theater
When AI makes you busy, not better — and how to tell the difference.
Recovery Guide
The 30-day plan for rebuilding the muscle the loop eroded.
The loop doesn't feel like a trap while you're in it. It feels like productivity.
That's what makes it dangerous.
— The Clearing