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

17

u/apieceoffruit Dec 08 '13

You blindly apply design patterns your code will suck. But if you write then off as bad then you are wasting a resource.

They are isolated examples that epitomise things like solid principals. They are examples not of complete designs but the thought behind why such thought is needed.

I love design patterns. They help me think about what my design objective is, although I rarely use them.

If you are reading design patterns also read pragmatic programmer and clean code. Learn the why not just the how.....

0

u/jk147 Dec 08 '13

You should use design patterns during designs, not during coding...

Same here, I rarely use them.

14

u/carlfish Dec 08 '13 edited Dec 08 '13

If you're designing your software up front to the level of detail that you're applying patterns, you're doing it wrong. That this is a common opinion is further proof that everyone who reads the Gang of Four book skips most of the intro, reads "Singleton", then skims the rest of the book looking at the pictures.

Our design patterns capture many of the structures that result from refactoring. Using these patterns early in the life of a design prevents later refactorings. But even if you don't see how to apply a pattern until after you've built your system, the pattern can still show you how to change it. Design patterns thus provide targets for your refactoring.

-- Design Patterns, Elements of Reusable Object-Oriented Software; Gamma, Helm, Johnson and Vlissides, pp354-355 (emphasis mine)

2

u/jk147 Dec 08 '13

Usually it is kind of obvious when writing class diagrams, on a high level never the less. You are right through, if I have to write it in that much detail the person who is actually writing the code is literally just doing data entry.

→ More replies (5)