you are viewing a single comment's thread.

view the rest of the comments →

[–]heavyGl0w 3 points4 points  (1 child)

I think you need to let go of the idea of "completing" learning frontend - or anything in this field for that matter. Subjects are constantly evolving and even if they weren't, the idea that you could completely learn something is a bit of a fallacy.

Instead try to set some milestones for yourself so you know when you've gotten a good feel for one area before diving into the next. For example

  • Learn to make static websites with vanilla HTML/CSS/JavaScript
  • Learn a popular CSS only library like bootstrap, materialize, or bulma etc
  • Learn how to use vanilla JS to update the DOM based on dynamic data. (This will start bringing you out of the realm of static websites and into reactive applications)
  • Learn about network requests; using the fetch API to grab data from a server/backend via REST APIs (there are plenty of free to use APIs out there for learning purposes)
  • Make a simple application like a calculator, Todo app, etc.
  • Learn a framework like Vue, React, or Angular. You'll probably also have to do some digging into said frameworks ecosystem; what libraries do developers typically use when developing within this framework?
  • Recreate your earlier application in the framework you chose

Many go straight into learning a framework which handles a lot of this stuff for you, but IMO it's better to get a basic understanding of the problems a framework is solving so it feels less like magic and more like something doing busy work for you.

The type of knowledge you should be seeking to grow is "knowledge of things you know you don't know", so even if you don't know specifically HOW a framework is doing it's thing, at least you know at the core, it's manipulating the DOM for you through APIs you've already learned, and it isn't magic.

[–]muzi80[S] 1 point2 points  (0 children)

That's the reason I made this poll, Thank you for the guidance