Aug 2026 • Article
Tutorials are a great way to learn syntax. They are a terrible way to learn how to actually build something. That gap became obvious the moment I tried working on my first project without a video guiding every step.
I followed a lot of tutorials early on, and I could reproduce almost anything I watched, step by step. But the moment I closed the tutorial and tried to build something of my own, I froze. I could follow instructions well; I couldn't yet make my own decisions. That gap is one nobody really warns you about.
My first real, unguided project was small - a personal portfolio, in fact, not too different from this one in spirit if not in code. No tutorial to follow, no one telling me the "right" folder structure. Just a blank editor and a vague idea. It was slower and far more frustrating than any tutorial, but every decision I made - however small - actually taught me something a tutorial couldn't.
Real projects are where I learned to be wrong constantly and not let it bother me. My first component structures were a mess. My first CSS was full of overrides fighting each other. But fixing my own mistakes taught me more than getting something right on the first try ever could, because I had to actually understand why it was wrong before I could fix it.
Tutorials often hand you a finished design to implement. Building on my own, I quickly realized how much thought actually goes into spacing, hierarchy, and consistency - things that look effortless in a well-designed site and fall apart immediately when you ignore them. Design stopped being someone else's job and became part of how I thought about every component.
Looking back, the lessons that stuck weren't the ones from tutorials - they were the ones from staring at my own broken code at 1am, trying to figure out why a re-render kept happening or why a layout only broke on mobile. Real projects force you to actually understand what you're building, not just recognize the pattern. That's the difference tutorials can't teach, no matter how good they are.
This site counts visits (masked IP, rough location, device type - never anything identifying) and publishes the results openly at /visitors.