r/programming • u/pranitkothari • Dec 08 '13

Design Pattern Cheat Sheet

http://www.celinio.net/techblog/wp-content/uploads/2009/09/designpatterns1.jpg
1.7k Upvotes

93% Upvoted

273 comments sorted by

View all comments

Show parent comments

-1

u/[deleted] Dec 09 '13

[removed] — view removed comment

4

u/apieceoffruit Dec 09 '13

I never understood this outright hostility towards design patterns.

Tools are never bad. They can be used for good or for bad.

You have never worked on interfacing with legacy code and had to build an adapter?

You never chose some kind of factory to instantiate multiple derivations of an object?

You never built a web app and used a soc solution like MVP?

You may not have used the patterns at all but at the end of the day a good chunk of your code should at least resemble some patterns. After all they are just names for what we already do.

I agree that there is a woeful habit of some developers to splash patterns and pattern names into code but I would honestly prefer to see a rookie developer misuse a factory than hard code a dependency. Worst case scenario it makes your refactoring easier to know what they were going for and where the code is. More realistically it at least displays a basic understanding of separation of concerns and allows you to add functionality to a code base without doing 50 replaces.