Do you think learning about design patterns is a good use of time? Or is it an old forgotten concept of the past, I wonder because none of the resources I’ve learned JS from (Books, Udemy, YouTube, etc) have ever mentioned this concept.
If it is worth my time, where should I begin?
They are good to know if another programmer mentions one in a code review or something. But I think a better way to learn commonly used patterns is to write code in an environment where there are some senior programmers. The more variety of people you work with the more high level patterns you’ll see and be able to choose from. If you want to see how often the documented patterns are used in the wild, choose one a week and see where and if you can find it in the projects you are working on. Or if your code could be improved by using that pattern.
I really recommend reading the Addy Osmani JS Design Patterns book linked in the post above! I wouldn’t say it’s critical early on, but once you start working regularly with frameworks like React, Vue, etc. it’s useful to read to understand the underlying systems these frameworks are using to achieve their magic. It will make you better JS programmer, and it will make reading more advanced articles on things like virtual DOM easier. There are some secondary benefits of reading expert-level code and patterns in JS like seeing the steps and concepts they take to keep things clean (encapsulation, separation of concerns, decorators), which I find myself appreciating and trying to implement more often the more time I code even with my frameworks. It’s even possible in a job some day you will need to write your own internal framework instead of use external ones.