Not because AI is bad. But because there's a stage in your growth where struggle is the whole point.

When you're a junior, you don't just need the answer — you need the friction. The 2-hour debug session where you finally understand what a stack trace is actually telling you. The moment you realize your mental model of how HTTP requests work was completely wrong. The pain of writing something that almost works and having to figure out why.

AI skips all of that.

It gives you the fish. Clean, cooked, plated. But you never learned to swim.

I'm not anti-AI. I use it. But I made a conscious choice early on to resist reaching for it every time I was stuck. To sit with the discomfort a little longer. To actually read the Django docs instead of asking Claude to summarize them for me.

The result? When AI does help me now, I can evaluate what it gives me. I can catch when it's wrong. I can build on it instead of just copying it.

That's the real skill gap forming in this generation of devs — not whether you can use AI, but whether you can think without it when you need to.

The devs who'll stand out in 5 years aren't the ones who used AI the most. They're the ones who used it wisely — after putting in the reps