Design Patterns

/prog/,

I'm now reading ``Head First Design Patterns."^[1]
When I'm finished, can I expect to be an EXPERT SOFTWARE DESIGNER???

Notes                                 
1. http://books.google.com/books?id=LjJcCnNf92kC

>>33
Completely seriously, UML-like constructs and design patterns are both very useful for the same thing: inter-developer communication.  Forcing strict compliance to the latest UML standards of modeling is fail.  Copypasta of design patterns is doing it wrong.  Overuse of design patterns is ALSO doing it wrong.  A peppering of a few UML like diagrams to show connections between things and enumerate their parts can be very helpful, especially when working with multiple developers.  Being able to say "the thing you're doing with that OBSERVER" is much more clear and concise than saying "the thing you're doing with that function/object that sends data over a specified interface to other functions/objects when an event or change occurs relating to the first function/object that the others may want to know about".