"I was debugging something in a language I've used for six years. I hit a wall. My first instinct — before I'd even tried — was to paste it into ChatGPT. I'd been doing that for months without noticing."
Yesterday I asked you to notice when you reach for AI.
Most people who write in tell me the same thing: they didn't realize how often it happens until they started watching for it.
One engineer said:
"I was debugging something in a language I've used for six years. I hit a wall. My first instinct — before I'd even tried — was to paste it into ChatGPT. I'd been doing that for months without noticing."
That's the moment.
Not a crisis. Not a breakdown. Just a quiet reflex that says: I don't try anymore.
There's a difference between using a tool and outsourcing your judgment.
When you use AI in your code, something different happens:
And slowly — without anyone announcing it — your relationship to your own work changes.
You stop thinking "I built this" and start thinking "this got built."
The things you used to just know, you have to look up again. Not because you're forgetting — because you stopped practicing them. The muscle isn't being used.
You spent years building an identity around being someone who can figure things out. When that gets replaced, you lose a piece of how you see yourself.
You know more than you're demonstrating. But the gap between what you know and what you do is growing. And every time you ship something you don't fully understand, you feel like a fraud.
"This isn't imposter syndrome.
This is different."
You ARE competent. But the code you're shipping doesn't reflect your competence — it reflects the AI's capability. And the more you lean on AI, the wider that gap grows.
You might have noticed: you take a vacation, you come back refreshed, you use AI heavily for two weeks, and by week three you're as tired as before.
That's because the problem isn't mental exhaustion.
It's that you've lost the thing that used to restore you: the feeling of having built something yourself.
Deep work is not just tiring in a bad way. It's tiring in a way that, when done well, also replenishes you. The flow state isn't just productive — it's meaningful. It gives you something back.
AI-assisted work doesn't give you that back. It gives you output without the nourishment.
That's why you can be busy all day and still feel empty at night.