Very nice and exhaustive article! In my experience, I've seen people misuse a lot of these patterns. How would you tell if for example the strategy pattern is not a good choice for your problem? Would be great if you could expand on that in your article.
Design patterns are solution to problems, not solution finding problems.
Design patterns are not silver bullet to every problem and if anyone is creating the problem just to solve it with a specific design pattern then it's very harmful.
IMO any solution should be rapidly prototyped first and then and only then if it's beneficial to implement a design pattern (or combination of them) we should approach for it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Very nice and exhaustive article! In my experience, I've seen people misuse a lot of these patterns. How would you tell if for example the strategy pattern is not a good choice for your problem? Would be great if you could expand on that in your article.
It's already mentioned in the post
Design patterns are not silver bullet to every problem and if anyone is creating the problem just to solve it with a specific design pattern then it's very harmful.
IMO any solution should be rapidly prototyped first and then and only then if it's beneficial to implement a design pattern (or combination of them) we should approach for it.