Read the post in Telegram: https://t.me/mike_in_web/5
When I started learning frontend, like a lot of people, I went through different tutorials and courses where the goal was to build some kind of project. The problem with this approach is that you're handed a solution.
You don't really get the chance to think things through or figure them out on your own, so you end up in a situation where, yeah, you know how to do something, but your skills become so narrow that if you're asked to do anything slightly different, you fall apart over the simplest stuff. In the end, instead of becoming a web developer, you turn into a “to-do list master,” building the same app over and over, just following the video like a script.
But when you work on a personal project, you’re the one asking the questions: “How do I make this work?” And that’s when real learning kicks in. You’ve got a need, you hit roadblocks, and you end up "reinventing the wheel." Your interest and motivation come naturally because every feature actually matters to you. And then, the best part of learning happens — those "Aha!" moments 😮.
It’s when you hit those roadblocks that you finally think, “Ah! So that’s what [insert tech here] is for,” or “Now I get why you’re supposed to do it this way!” It’s not just some empty lesson you learned because “that’s just how it’s done.”
And what’s cool is that these kinds of projects really help during interviews. You’re not just showing off some tutorial code; you’re showcasing solutions you came up with on your own. That immediately sets you apart from the people who just churned through a course.
So don’t just follow someone else’s plans. Solve your own problems, and your learning will be way more interesting 💫.
Follow me in Telegram: https://t.me/mike_in_web
Top comments (0)