Many people ask me how to organize their studies in technology. There's no single path, but it's possible to think in learning levels that provide clarity and direction.
I've put together a list of items to make studying easier, going from the basics to advanced.
Many people still associate the term frontend only with the visual appearance of a website or application — colors, buttons, layouts.
That famous phrase "it's just a button." But they don't understand what's behind that simple button that triggers multiple actions in the user interface and, in most cases, in other systems via API, for example.
Front-end development is frequently misunderstood. Many people still limit its definition to the purely visual layer — "just put a button there" or "just need to change that color." This misconception underestimates the complexity and impact that architectural decisions have on modern web development.
And with the rise of Vibe Coding, this view can be amplified. Frontend is just HTML and Backend is a bunch of CRUDs.
Those who work with development know that's not how it works. A simple system built in 1 hour that scales? Good luck.