The Fading Urge to Figure It Out
The Opening
Try to remember the last time you had a genuine, almost physical urge to figure something out.
Not "I need to know this for the project." Not "My manager asked me to investigate." Not even "I should understand this eventually."
Just: I want to know how this works. Right now. I can't let it go.
When was that? What were you working on?
If that memory comes easily — if you can point to something from the last few months — you're probably still in the habit.
If it takes you a while to find one, or you can't find one at all, that's not a personality flaw. That's a signal.
What You're Noticing Is Real
There's something that happens to curiosity when you have a tool that can answer anything instantly.
It doesn't go away entirely. But it changes shape.
The specific transformation I'm thinking about is this: the question used to come first, and the understanding used to be the reward. You got curious, you investigated, you learned, you felt the satisfaction of knowing. The journey and the destination were the same experience.
With AI-assisted work, the destination changed. The destination became shipping working code or having an answer to give in a meeting or finishing the code review quickly. Curiosity still flickers — you still wonder why something is happening — but there's a shortcut to "knowing." You ask the AI, you get a plausible explanation, you move on.
The explanation feels like understanding. Sometimes it is understanding. Often it's something thinner: recognition without comprehension. You can describe what the system does without being able to predict what it will do in a novel situation.
And here's the part that nobody talks about enough: the shortcut works well enough, often enough, that you stop noticing the difference. You stop noticing that you used to need to understand things — that understanding used to feel non-negotiable — and now it feels optional. Something you do when you have time, or when it's professionally required, or when someone asks you to explain it.
Curiosity used to be a drive. Now it's a habit you're slowly losing.
The Specific Thing That's Atrophying
I'm not talking about knowledge. Knowledge can be looked up.
I'm talking about the specific skill of sitting with a problem long enough to develop a feel for it. The kind of understanding that comes from being confused, pushing through the confusion, having a wrong model, testing the wrong model, revising it, and finally arriving at a model that matches how things actually work.
That process — productive struggle, as cognitive scientists call it — is not just how you acquire knowledge. It's how you develop what engineers call intuition. The ability to sense that something is wrong before you can articulate why. The ability to ask the right question because you have enough feel for the problem to know what you don't know.
AI doesn't just give you answers. It gives you answers before you've developed the feel for the problem that would let you ask the truly sharp question.
And here's what nobody tells you: feel doesn't transfer. You can't receive it secondhand. You can't get it from reading an AI explanation of what the code does. You get it from spending time confused and eventually finding your way through.
Every time you take the shortcut, you defer that process. And defer it again. And defer it again. Until the urge to sit with a problem long enough to really understand it — the thing that made you a good engineer in the first place — starts to feel like a luxury you don't have time for.
It used to be the job. Now it feels like a productivity tax.
The Thing That Makes This Hard to See
You can't feel the loss of a drive the same way you can feel the loss of a skill.
If your coding ability declined, you'd notice — you'd feel slower, less certain, more dependent. But curiosity fading isn't experienced as curiosity fading. It's experienced as: I don't really need to dig into this. I'll just ask the AI. I can always look it up later if I need it.
The "later" doesn't come because the AI always has an answer for right now.
This is the specific pattern: you don't notice you're losing the urge to understand things, because every time the urge arises, there's a very easy, very fast way to make it stop. And the ease of that solution makes it seem like the urge wasn't that important to begin with.
But it was important. That urge — the one that made you read source code for fun, that made you stay up figuring out why something was breaking, that made you take apart the abstraction to see what was underneath — that urge is part of what made you good at this. Not all of it. But part of it.
You can't afford to lose that part. Not because understanding is intrinsically valuable (though it is), but because the judgment to know which things are worth understanding deeply — that's not a skill you can outsource. That's exactly what sits underneath the ability to use AI well and the ability to catch when AI is wrong.
The Practice This Week
Here's the thing I'd ask you to notice this week:
Resist One Shortcut
Pick one thing — just one — where you feel the urge to understand something, and resist the urge to ask AI first.
Don't fight every time. Don't make it a rule. Just: when you notice genuine curiosity arising, pause and see if you can sit with it for a few minutes before the shortcut.
This is not about masochism. It's not about refusing to use good tools.
It's about keeping the muscle alive. The muscle that says: I want to understand this because understanding it is part of what I do. Not because someone told me to learn it. Not because it's on a rubric. Because it's mine to know and I want to know it.
The AI will still be there when you're done. It will still give you a faster answer than the struggle would have. But the struggle is not just friction — it's the process by which you develop the feel that makes you dangerous in the way that matters.
One More Thing
I want to be careful here because I know how this can read. This is not a lecture about whether AI is good or bad. It's not a pitch for "use less AI" or "try harder." That's not the point.
The point is something more specific: the engineers who will do best in this era are not the ones who use AI most or least. They're the ones who maintain the judgment to know when to use it and when to sit with the problem themselves.
That judgment is not an AI capability. It's a human one. And it doesn't stay sharp on its own.
The question worth asking this week is not "Am I using AI enough?" or "Am I using AI too much?" It's: Do I still have the urge to understand things before I ask someone to explain them?
If the answer is yes, protect that. If the answer is that it used to be yes and it's not anymore, that's worth sitting with.
Not to feel bad about it. To figure out whether you want it back.
If this Dispatch lands for you, share it with an engineer who needs to read it.
The Clearing — clearing-ai.com