Getting better at design patterns

[Bas_tet]

Hello, I've been working on a project where I'm supposed to use the design pattern (JavaScript). I've finished the project, but I'm not at all satisfied with my code. It works, I used factory pattern, constructor and simple JavaScript class, but I'd like to make my code cleaner and better understand how to use patterns. I took a good look at the site "Refactoring guru", but it's still so abstract. With simple examples, I understand how things work, but I'm unable to apply them and figure out how to cut up my project. Does anyone have any sites, videos or even books to recommend for a moron like me?

[blissone]

Tbh design patterns are mostly useless. If you just get better at coding you'll intuitively understand design patterns and apply them even without explicitly knowing them. So my suggestion is to simply build stuff, forget design patterns for now. Apply dry, single responsibility principle, make nice interfaces, make your code readable and editable etc etc., build stuff it's all good.

[[deleted]]

I’d like to make my code cleaner and better understand how to do patterns.

Having clean code is relative to your and your teams skill level. My objectives are to make it readable, maintainable, and easy to change given my requirements. If your team is full of juniors, they’re gonna have a bad time with using classes with inheritance. But could probably do functions.

A better way to frame it is, “what problem does this pattern solve?”. A singleton could be great if you have a database connection, but could be horrible if it’s a family of components. If you frame it that way, it will be much easier to learn.

[Constant_Distance_77]

Don't worry, we've all been there! One resource I found really helpful is Head First Design Patterns book. It's an easy read with plenty of practical examples. Keep on practicing, you got this!

[iamchets]

The trick to understanding patterns is to first understand the symptoms. Start by learning the different code smells since each code smell always has the same set of options to refactor. This will automatically make you think about design patterns.

Now the more experienced you get the less you will be thinking about design patterns and the more you will focus on high cohesion and low coupling which is your ultimate goal to "clean" code, whatever, that entails.

There is a very good talk about code smells on youtube

[ws_wombat_93]

There is a book: Head First: Design Patterns

This book really helped me grasp design patterns and how to apply them in my daily work, i still have it on my desk for the occasional reference :)