I stopped collecting tutorials and started building smaller projects
For a while, my learning process looked like this: Tutorial → notes → another tutorial → another technology → repeat. I was learning a lot, but it wasn't always translating into the ability to build something from scratch. What I've been trying instead is a much simpler loop: Learn one concept → build something small → get stuck → debug it → document what I learned → move on. For example, instead…
The author's learning process used to involve following tutorials, taking notes, and then moving on to another tutorial and technology in a repetitive cycle. While they gained a lot of knowledge, this approach didn't always result in the ability to create something from scratch. To address this, the author has adopted a simpler learning loop: learning one concept, building a small project with it, encountering challenges, debugging those challenges, documenting the lessons learned, and then moving on to the next concept.
For instance, instead of investing days in mastering a framework before using it, the author now builds a small feature with it. This allows them to discover any missing pieces of knowledge when they actually need it. By embracing getting stuck as part of the learning process rather than trying to avoid it, the author has found this approach effective.
They are still experimenting with this method, but one advantage they appreciate is that their learning produces tangible results – instead of accumulating more folders filled with saved tutorials.
The author asks fellow web developers, programmers, and career professionals, "What's one learning approach that actually helped you move from 'I understand the tutorial' to 'I can build this myself'?"
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
