AI is an incredible learning tool. I said it in my previous article, and I still believe it.
But after spending months learning new web frameworks and technologies with AI as my main companion, I noticed something uncomfortable.
I was moving fast. But was I really understanding?
The old way was painful and powerful
Before AI, learning a new technology meant suffering.
You'd hit a bug. You'd search for hours. Read Stack Overflow threads, YouTube videos. Try things that didn't work. Get frustrated. Sleep on it. Come back the next day and finally click. It works.
That process was slow. Sometimes humiliating. Often exhausting.
But here's what I didn't realize at the time: that struggle was doing something to my brain.
Every hour spent searching, failing, and retrying was building a deep, almost physical understanding of the concept. When I finally found the solution, I owned it. I knew not just the answer, but every wrong path around it.
Now I just ask. And get an answer. Instantly.
With AI, that whole painful loop collapses into a single message.
Bug? Ask AI. Confusing concept? Ask AI. Don't know the right syntax? Ask AI.
The answer comes in seconds. Clean. Well-explained. Usually correct.
And I move on.
The problem is: moving on is not the same as understanding.
What I actually noticed
Learning Vue, Nuxt, and other web technologies with AI, I realized something: I needed to build far more projects than before to reach the same depth of understanding.
Without AI, one difficult project could teach me something deeply because I had wrestled with every problem alone.
With AI, I could finish that same project twice as fast, but the understanding was shallower. I had to build three or four more projects to reach the same level of genuine comprehension.
The friction wasn't just wasted time. The friction was the learning.
This doesn't mean AI is bad for learning
I'm not saying we should go back to suffering alone for hours.
What I'm saying is: we need to be intentional.
A few things that help me:
- Try first, ask second. Before asking AI, I give myself at least 15-20 minutes to struggle alone. The struggle primes my brain to actually absorb the answer.
- Ask AI to explain, not just fix. Instead of "fix this bug", I ask "why is this happening and what does it teach me about how this framework works?"
- Build more, copy less. More small projects from scratch. Less copy-pasting AI-generated code without understanding it.
The bottom line
AI accelerates learning. But depth still comes from doing really doing and from the discomfort of not knowing yet.
The goal isn't to avoid AI. It's to use it without losing the struggle that makes knowledge stick.
Have you felt this too? Are you learning faster but sometimes feeling like things don't fully sink in? Let's talk in the comments.
Follow my journey on Facebook I share thoughts on tech, learning, and building in the open.
Top comments (1)
Hey everyone 👋
I wrote this article after a very specific moment, I had just finished a Nuxt project with heavy AI assistance, and realized I couldn't fully explain some of the choices I had made in my own code.
That was a wake-up call.
I use AI every single day. I'm not against it at all. But I think we don't talk enough about this side of it; the risk of moving fast without truly understanding.
Would love to know: do you have a personal rule or habit to make sure you're actually learning, and not just shipping? 👇