Every developer knows how Tutorial Hell feels: being stuck in a loop.
You wanna get out, but you can't.
Why?
'Cause of the fear of failing while building something real, making mistakes, and realizing that you may not have enough knowledge.
And in case you don't know what Tutorial Hell is, I'll explain it!
We can divide it into 2 parts:
- Pre-AI era
- AI era
Pre-AI Era
Tutorial Hell in the pre-AI era is when you watch YouTube videos to learn things, and you learn the fundamentals, but as you keep learning, you get addicted to building by watching YouTube tutorials. And if anyone gives you something to build, you wouldn't be able to build that thing by yourself.
Why?
'Cause you never trained your brain to solve problems and build things by yourself.
For example: A developer builds an authentication system by following a tutorial. Later, someone asks them to implement authentication in a different project. They don't know where to start.
AI Era
Next is the AI era. So, how does Tutorial Hell still exist when we don't even watch things to learn? We prompt new things and build them!
Learning the fundamentals is fine, but once you cross the barrier where you start understanding things by yourself, you should start building things yourself. Try to sit with a problem and solve it. If you can't do it and go to AI every single time with prompts like "solve this" or "fix this", you're falling into the same trap.
You may feel that you're learning 'cause you're building! But NO!
You may feel that you're learning, but knowledge retention is relatively lower. Generating solutions without actively solving and understanding them by yourself can result in poor retention.
Building with AI is not bad as long as you know how it's working under the hood!
Entirely depending on AI for learning is bad!!
These are the common issues a developer faces in their beginner days.
So, how do you overcome this?
-
Start by building without a tutorial: As you gain fundamentals and get through Tutorial Hell, pick a project, a small one. Figure out what you want to build and implement it by yourself. If you get stuck, ask Google, not AI, 'cause AI gives you answers directly.
-
Struggle before asking AI: When something doesn't work and you have the urge to ask AI, give yourself an extra 20 minutes. Try to solve it, do FAFO (Fuck Around & Find Out), and if you still can't solve it, then ask AI.
-
Use AI as a teacher, not a developer: If you take a solution from AI, ask why it works, what was different in your code, what alternatives exist, and what would happen if you changed the implementation.
-
Rebuild what AI gives you: Close the generated solution and try implementing the same functionality independently from memory.

