I didn't start with bad intentions.
Tutorials felt like the perfect way to learn. Someone experienced guiding you step by step, explaining things, showing best practices. It felt efficient.
And for a while, it worked. I was building things quickly. New features, new projects, new tools. Every few days, I had something new to show. It felt like progress.
But something strange started happening. The moment I stepped outside the tutorial... everything slowed down. A small change would break things. A slightly different requirement would confuse me. And suddenly, the confidence I had while following the tutorial disappeared.
I could follow. I couldn't think.
That sentence bothered me for weeks. Because I was putting in real time. I wasn't lazy. I was just training the wrong muscle.
That was the uncomfortable truth. Tutorials gave me the illusion of understanding. Because when someone else is making decisions for you, it feels like you know what's happening. But you're not solving problems. You're watching solutions unfold.
There's a big difference.
And once I saw that difference, I couldn't unsee it. I started noticing the same pattern everywhere:
I remember trying to build something on my own after finishing a tutorial. Same stack. Same concepts. Nothing new. And still, I got stuck. Not because it was hard - but because I had never actually practiced thinking.
That realization was frustrating. I had spent so many hours "learning," but I couldn't trust myself to build something from scratch. I wasn't learning to build. I was learning to follow.
The fix wasn't to completely stop tutorials. That would've been unrealistic.
Tutorials are still useful. They're just dangerous when they become your default environment. Because real projects don't come with a narrator.
Instead, I changed how I used them. I stopped coding along. That was the biggest shift.
I'd watch a part, pause, and try to build it myself. Not perfectly. Not efficiently. But from memory. And most of the time, I'd fail.
That failure was important. Because it showed me exactly what I didn't understand. Earlier, tutorials hid those gaps. Now, they exposed them.
I also added friction on purpose. After each section, I'd close the video and write down:
If I couldn't answer, I rewatched with intent. Not passively.
I also started doing something uncomfortable again. I'd deliberately not look at the tutorial when stuck. I'd try multiple approaches, even wrong ones. It took longer. It felt worse. But it built something tutorials never gave me: Decision-making ability.
Over time, I noticed a shift. I wasn't just copying patterns anymore. I was starting to recognize them. Why this hook is used here. Why this structure works. Why this breaks.
That's when tutorials became useful again. Not as a crutch. But as a reference.
That was the biggest change. Reference helps your thinking. Crutches replace it.
I still watch tutorials. But now I watch them like a mechanic, not a tourist.
I pay attention to decisions. Why this file structure. Why this state boundary. Why this trade-off.
And if I can't rebuild the idea without the video, I don't count it as learned yet.
Finishing content is easy. Building confidence is harder. But that's the work that actually transfers when you're alone in a real project.