Rating  - Good book for Software Designers
It is a good direction for the Software Engineers to learn about patterns and designing the applications.
Rating  - best design patterns book
This is the best design patterns book ever
language is simple.
examples are usefull
this is a must-have book
Rating - A must have for developers and designers
Design Patterns is an essential book for every software developer or architect. It was ground breaking for it's time, describing reusable design patterns that recur in software development projects.
The presentation used makes reading and understanding the concepts easy, and allows one to learn and apply the patterns a few at a time. It's a great reference book, and the distilling and naming of the patterns really aids communication between developers.
Rating - Ages very well
There are few books in the software industry that hold up for any length of time. This is one of the exceptions. In my work, I refer to this book periodically and find that it offers more over time. This book should be on the shelf of most object oriented programmers.
Rating - odi et amo
Object orientation is about dynamic binding, encapsulation, inheritance, and polymorphism. It's not necessarily about 20 patterns and their permutations. If you understand the basics, then you're set. But unless you're in an environment like Smalltalk where you can see OO unadulterated, then GoF is the next best thing.
The authors carefully format their presentation, and cross reference patterns for completeness. They review double dispatching (callbacks), pluggable adapters, lazy initialization, factories, deep vs shallow copying, and delve into detail, showing how misapplications can lead to unintended consequences.
GoF emphasizes early on that inheritance is overused. There are too many deep, inflexible layers of inheritance out there, a habit GoF helps snap.
Sometimes though, they lose the forest in the trees. Key ideas get lost in sub-topics, and while it took me awhile to be convinced that some patterns had a unifying idea, others are redundant.
For example, a Strategy is similar enough to a State pattern, since both extend functionality conditionally through collaboration rather than inheritance, and both will likely involve callbacks and fit the Visitor pattern as well. And instead of the Adapter, Mediator, and Observer patterns, I would have preferred a generalized discussion on event dependency and pluggable adapters with specific examples in increasing complexity and differentiation.
But there's an allure to the idea of 'patterns', and it helps sell components. 'Polymorphism' and 'Smalltalk': bad marketing. They sound like diseases and phobias. The names were fine in the early 90s, but now they are marketing to a wider audience upon whom those fine points will be lost. 'Patterns' and 'Java': good marketing.
All cynicism aside, this book is the only comprehensive analysis of object-oriented design patterns, with examples from programming languages mainstream and obscure, and goes so far as to advance an abstract set which we can all share. Now, whether or not seasoned developers will toss their old semantics out in favor of these is debatable, but younger programmers may find this reference to be their generational touchstone. Architects of any stripe should find something to ponder within its pages.
Go to the Product Information page
page 8 of 10 3 4 5 6 7 8 9 10
Customer Reviews for Addison-Wesley Professional,0201633612,785342633610,9780201633610,0201633612,005.12 |
