| | ||
| | | |
| |||
| |
|
| |
![]() | ![]() |
|
| | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
![]() Accounting & Finance Architecture Arts & Photography Business & Investing Business Management Computer Science Apple Education Business & Culture Certification Central Databases Digital Music Digital Photography & Video Games & Strategy Guides Graphic Design Hardware Home Computing Microsoft Mobile & Wireless Computing Networking Operating Systems Programming Project Management Security & Encryption Software Web Development Engineering History Humanities Law Medicine Professional Science Reference Science Social Sciences Summaries and Customer Reviews are supplied by Amazon.com
Customer Reviews:Average Customer Rating: Accomplishes its goal Design Patterns set out to identify the some of the most commonly used patterns and name them, so that they can be discussed easily. It does precisely that, and quite well. As long as you remember that it is not meant to be the definitive description of any patterns, and that variations and combinations on the patterns described are not only allowed but encouraged, it is a good reference. I would recommend that anyone interested in object-oriented design at least skim it, if for no other reason than to extract the vocabulary it introduced. Great if you live in the 90's This book reminds me why I hated school so much, despite my innate love for programming. It is bland, boring and outdated. If it had pictures in it, I would have drawn mustaches on all the people. There is nothing about the way this book is written that engages the reader and makes them want to read more. The examples are outdated, and don't directly apply to developers using modern languages like C#/Java. I mean using sub-classing for method callbacks is one such example, gimme a break. With that said, this book I'm sure was groundbreaking when it was written when a lot of this stuff was not well known. However, being a programmer of the modern age, most of these patterns are intrinsic and intuitive. Most of these patterns I've used throughout my career, I just didn't know what they were formally called. So, if you want a book that puts a name with the common patterns you normally use day to day, by boring you to death in the process, then this is the book for you. If you are a teacher and want to fail your whole class and discourage them from pursuing CS as a major, then this is definitely the book for you. A little over my head This book is just "OK" for me but that's only due to the fact that I don't know SmallTalk or C++. I was able to follow the descriptions of how the design patterns work, but that's because I already read the Head First Design Patterns book, which for me was a much better instruction on Design Patterns. Great book, but JAVA programmers beware First let me start with the good points about this book. Excellent Place To Start This is an excellent place to start when you have a problem. It won't do the work for you, but it will get you off on the right foot. | | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ![]() | |
| |