Learning frontend development is NOT a checklist

Learning something new should be simple.

You figure out what you need to learn, start studying, and keep moving forward until you get where you want to be. And when you start learning frontend development, the path seems pretty clear:

HTML, CSS, and JavaScript.

You watch videos, take a free course here and there, follow a few tutorials, and start building small projects. Everything goes well… until you try to build something on your own.

That’s when you start encountering needs that weren’t on the initial list. A library, an API, a backend, testing…

The foundation everyone seemed to agree on quickly turns into a list that seems to have no end. And with every new technology come new questions: how much do I need to know, when can I move on to the next thing, and, above all, what does it actually mean to have learned something?

When you start studying web development (or any professional career, I’d argue) it’s easy to imagine that there’s some kind of checklist you’re supposed to follow and. But you quickly realize that learning goes beyond simply “mastering” technologies.

It’s a much more structural process, where the important thing is to transform that checklist into a network where technologies connect and build upon one another, while you gradually develop logical and algorithmic thinking and start developing other skills too: the ability to find information, understand documentation, frame problems, find solutions and gain experience.

There’s nothing wrong with building personal projects to gain experience using the technologies and resources you’ve learned. But here you run into a paradox:

You need experience to get a job, but you need a job to gain experience—and in the meantime, you keep studying.

And the cycle repeats itself: you learn a new technology, then another, build a project, improve it, and discover that there’s yet another thing you didn’t know existed.

When do you know that you know enough? Where do we draw the line?

I don’t think there’s a simple answer to that but I do think this situation reveals a problem with the way we tend to think about learning: maybe we’re using technologies as our unit of measurement.

The more you build, the more you realize that learning doesn’t work the way you initially imagined.