Rating: 
Summary: The best, so far...
Review: Yes, the book does have some 'funky' examples for which we need other examples (i.e. swimming) to understand. I have read most of the patterns books and this one is by far the clearest and best written. The author uses example code with GUI components, which helps the reader bridge the gap between the abstract and the concrete. I don't mind the typos since I consider them an integral part of the learning process. I also take in consideration the fact that no product, book...is ever going to be perfect. But again, typos are an aberration to any beginner trying to 'swim' through the murky waters of a new language or concept. Learning patterns tend to be a difficult task. The frustration of many people will show in the low rating they give most of the patterns books. To measure the return on investment of a book is to know whether a book has advanced my knowledge and thus added real value to the software I write. In this case, it is a resounding yes. The Gang of Four book (GOF) is 'the pattern book'. Problem is, there are no examples, unless you have C/C++ background, which I don't have. I admit that GOF is the best-written patterns book, but the lack of good examples makes it almost useless. Cooper has an excellent column in JavaPro magazine called JavaTecture in which he writes about design patterns, different Java technologies, and coding tips and techniques. Thankfully, his work for the magazine is well edited and is just one of many tools I use to expand my Java knowledge.
Rating: 
Summary: The author doesn't understand the patterns he's explaining
Review: I liked the writing style of this book. It is much clearer and understandable than any other pattern book out there, but it has one major flaw... the author doesn't understand patterns either! Here's one example... Template. Easy! Take an algorithm, put it in an ancestor class and extend it, then implement the steps of the algorithm. I just explained it. However, Cooper misses the most important part: the algorithm!! Instead, the section labelled "Template" is in fact not about the Template pattern, but a decent explanation about how to use abstract classes. I looked in my copy of GoF and re-read the Template pattern section. It's only about 10 pages long and is explained fully on the first page. This may be the worst example from the book, and other templates he explains pretty well. For someone new to patterns however, it's very misleading if every third pattern isn't correct.
Rating: 
Summary: More "Duh?" than "Aha!" experience from this book!
Review: Is there something wrong with the book? Or is it just me. But I think the author is having a hard time explaning his ideas. Anybody having the same experience with this book?
Rating:
Summary: This was a joke!
Review: I was not able to compile anything from the textbook! The code on the CD did not match the code in the book and furthermore were even different examples.
Rating:
Summary: Good pattern book
Review: If you have read the GOF pattern book and need to translate all the good ideas from the book to Java, this is the book for you. The author manages to give good examples of all the patterns, the code works just fine. There is a good reference at the end of the book that explaines the patterns in the swing libraries. To summarize, this is a really good book. However, if you are new to programming you shouln't read pattern books yet. Do some programming first and then read pattern books! /Cheers
Rating:
Summary: Distracting Typos
Review: I'm compelled to add a 'me too' to the complaints about type-setting. This book's errors are such a distracting mess that it is a disappointment. If you are a Java developer desperate for a Java-centric treatment of patterns, and you are thinking this book is a slam-dunk for your library because it fills that niche -- think again and proceed cautiously -- or simply spend the money considering this a place where you'll get a few tid-bits that will help you on your path.
Rating:
Summary: Unnecessary.
Review: This book basically unreadable without the Gang of Four book. And if you already have the Gang of Four book there's no reason to buy this book.
Rating: 
Summary: Ray of Hope
Review: This book showed me a ray of hope when I was bogged with GoF patterns book.But there is a bit disappointment in the way author explains Factory Method pattern,I couldn't get what he was trying to tell ,the swimmers example was way too complex for the scenario.But the rest of the book is flawless he covers all the patterns successfully.But I always have a question How many more books do I have to buy ?
Rating:
Summary: Inaccurate, filled with typos, poor examples.
Review: There is a tremendous need for a good, readable book that teaches design patterns in a way that the average reader can understand and follow and which uses Java for code examples. Unfortunately, this is not that book. In a session at JavaOne 2000, the author stated that he wrote this book as part of his process of learning about patterns, and it's clear throughout the book that he didn't have a full grasp of the patterns he was writing about. For example, on page 80 he mistakenly identifies Java's AWT adapter classes (such as MouseAdapter) as being examples of the Adapter pattern. They are not. In addition, as other reviewers have pointed out, the book is riddled with typos and also suffers from poorly chosen code examples. Given all these problems, I cannot recommend this book at all for anyone interested in learning more about patterns. As hard as it is to read and understand at times, the Gang of Four book is still your best bet.
Rating: 
Summary: extremely irritated
Review: i think this book was written with good intentions, to function as a tutorial or a help-guide to the densely written "Design Patterns" , or to provide java examples in a more readable way. so far, i like the way book is organized and the way he explains the concepts that i couldn't understand just by reading the original book. however, the examples are from hell!! why in the world would the author think that the general readers would be familiar with 'seeding', and 'heating' in swimming competition? and different types of gardens? i understand you are a swimmer and a home-owner but that's not a proper reason to make readers confused.
| 
