1 of 1 people found the following review helpful
Tedious and long winded if you are experienced,
Verified Purchase(What is this?)
This review is from: Design Patterns Explained: A New Perspective on Object-Oriented Design (Software Patterns) (Paperback)
It's easy to read but tedious if software design is not new to you. The book reads like the author chatting to an inexperienced developer and trying to instil his own personal experience. Personally I don't want to read about someone else's career. I want to be able to put names to patterns that I have frequently had to derive myself so that I can demonstrate at job interviews that I know about patterns.
A pattern is a solution that comes up enough times that it might as well have a name. By their very nature patterns are obvious solutions if you understand the fundamental principles of software engineering and think about the problem for long enough. The problem almost always defines the solution. Unfortunately this book tries to describe a new perspective on Object Oriented design that frankly just isn't actually new. As with any technology, how it is actually used in practise evolves over time and changes from how it was first envisaged. Whilst reading this book a colloquial expression often came to mind that Dr Watson could have said to Sherlock Holmes if he had just stated the blindingly obvious.
This is most definitely not a reference book. You have to wade through bumpf about design and the personal experiences of the authors to find the sections describing specific patterns. Concise is not a word that I would use to describe this book. It's useful to know the names of patterns because it aids communication with other engineers, but if you want to find out what someone else is referring to then it will be faster to use wikipedia.
The only thing that I really learnt from this book was about the pitfall of implementing double checked locking in Java. Unfortunately Wikipedia gave a much more useful explanation.