The feeling you've been hiding from your team? That's the signal.

What You Actually Feel

If you've been at a computer for the past few months, you've probably noticed some version of this:

• You open a task. You get to the interesting part. You hand it to AI.
• You used to know how things worked end-to-end. Now it's a blur.
• The code you ship feels like it belongs to someone else.
• When someone asks "how did you build that?" — you freeze.
• Sunday nights feel like a form of dread, not preparation.
• You're tired in a way sleep doesn't fix.
• You've started avoiding the parts of your job that used to excite you.

Sound familiar?

You might have tried to explain it to someone. Maybe a coworker. Maybe your partner. You probably said something like "I just feel off" or "I'm in a rut" or "I think I need a vacation."

They probably said "yeah, totally, I get that too" — and moved on.

Because nobody's named it yet.

There is a name for this. It's called AI Fatigue.

And it's not about being bad with tools, or being resistant to progress, or being "old school."

It's about what happens when the thing you spent years learning to do gets outsourced to a machine — and nobody talks about what that does to your sense of self as an engineer.

The problem isn't that AI exists. The problem is that we built an industry around code-as-craft, and then we made that craft trivially replaceable, and then we acted surprised when engineers started feeling like something was wrong.

That's not laziness. That's your brain adapting to a new reality — but not a healthy adaptation. It's a kind of Learned Helplessness applied to your own expertise.

The problem isn't that AI exists. The problem is that we built an industry around code-as-craft, and then we made that craft trivially replaceable, and then we acted surprised when engineers started feeling like something was wrong.

You spent years building the ability to understand a problem deeply before solving it. To write code and know why it works. To debug by understanding the system, not by guessing. To make architectural decisions based on trade-offs you actually understand. To feel genuine craft satisfaction when something ships well.

Now you're watching a junior engineer paste in a prompt and get something that looks like your work, faster than you could have.

And then you watch yourself reach for AI to do the parts that used to be yours.

That's not laziness. That's your brain adapting to a new reality — but not a healthy adaptation.