Hi Eddie! Pure/vanilla JS is always a good thing to master. It's the base of "our world".
But what you say about the next wave of trends is actually a hot topic with me too. I have been, and still am, working very hard to catch up with the previous trends and I also feel this new wave coming. But what I find hard is: how to keep up with all the news and filter out what's a fluke or what's the next Angular/React/whatever.
I have a few perspectives on your great questions.
Separate the core concepts in order to learn more efficiently
Try to separate frameworks into two categories: Design Patterns and Syntax. The Syntax is the easy part and just requires time to commit to memory. The Design Patterns is the one that is the most challenging to overcome, because it requires you to set aside any notion you may have on how to structure and architect an application. If you can understand the underlying Design Patterns of a particular framework, this will actually help you learn the next wave of frameworks much quicker. This is tough because you have to open yourself up to understanding someone else's opinions.
Frameworks are just that - someone else's opinions
If you keep this in the back of your mind, then it will allow you to approach your learning with healthy skepticism. If you feel that the prescribed approach of a framework is cumbersome compared to your prior experiences, then that is a valid point and you're probably not the only one who feels this way.
On keeping up with trends
Your question about keeping up reminded me of this great video from the creator of Django - A Framework Author's Case Against Frameworks.
I do advise you to stay up-to-date on incoming trends just to see what's coming, but I don't think that you should be stressing about mastering every single one. If you're constantly following the shiny object, you're not making yourself resilient to the ever changing dev industry. Here is a great article on this topic The Brutal Lifecycle of JavaScript Frameworks.
Hi Eddie! Pure/vanilla JS is always a good thing to master. It's the base of "our world".
But what you say about the next wave of trends is actually a hot topic with me too. I have been, and still am, working very hard to catch up with the previous trends and I also feel this new wave coming. But what I find hard is: how to keep up with all the news and filter out what's a fluke or what's the next Angular/React/whatever.
I have a few perspectives on your great questions.
Separate the core concepts in order to learn more efficiently
Try to separate frameworks into two categories: Design Patterns and Syntax. The Syntax is the easy part and just requires time to commit to memory. The Design Patterns is the one that is the most challenging to overcome, because it requires you to set aside any notion you may have on how to structure and architect an application. If you can understand the underlying Design Patterns of a particular framework, this will actually help you learn the next wave of frameworks much quicker. This is tough because you have to open yourself up to understanding someone else's opinions.
Frameworks are just that - someone else's opinions
If you keep this in the back of your mind, then it will allow you to approach your learning with healthy skepticism. If you feel that the prescribed approach of a framework is cumbersome compared to your prior experiences, then that is a valid point and you're probably not the only one who feels this way.
On keeping up with trends
Your question about keeping up reminded me of this great video from the creator of Django - A Framework Author's Case Against Frameworks.
I do advise you to stay up-to-date on incoming trends just to see what's coming, but I don't think that you should be stressing about mastering every single one. If you're constantly following the shiny object, you're not making yourself resilient to the ever changing dev industry. Here is a great article on this topic The Brutal Lifecycle of JavaScript Frameworks.
Thanks Eddie, that are some great insights. I'll check out your links/videos asap :-)