Rating:  Summary: I REFER TO THIS BOOK OVER AND OVER Review: This is one of the best OO reference books around. The useage examples are sometimes obscure, but the concepts are solid. This is one of five books that follow me to every jobsite.
Rating:  Summary: a must read, but a very tough read. Review: The authors define design patterns as: descriptions of communicating objects and classes that are customised to solve a general design problem in a particular context. A design pattern names, abstracts, and identifies the key aspects of a common design structure that make it useful for creating a reusable object-oriented design. The design pattern identifies the participating classes and instances, their roles and collaborations, and the distribution of responsibilities. Easy to wrap your mind around, eh? Design Pattern people are in love with the power of abstraction and generality. You might even say they prefer to impress rather than inform. However, somehow you are going to have to learn this stuff, even if only to get into the heads of the guys who designed the AWT. Try starting with the code samples in the Design Patterns book. You have to read this book at least twice before it begins to make any sense. However, if you want to call yourself a programmer you MUST understand this book. I hope somebody writes a version of this book for Java programmers. It is written from the perspective of C++ and Smalltalk. This is a book where the you want the hardcover version. You go back to it again and again.
Rating:  Summary: This is a book okay to read, but.... Review: I think this book presents a number of design patterns, but, same as other reviewers says, I feel that this book need more examples, especially those that solve the entire real-life project. Also, some of the patterns are trivial, not really a great idea, but they are covered in details.
Rating:  Summary: Potent, pure, perfect Review: This book transcends code theory and becomes an almost philosphical text on the nature of proper architecture and use/reuse. You can apply the object theories in here to not only programs, but production methodologies, business models, artificial intelligence, and anything else using modular structure.An ability to grasp abstracts is required, but apart from that, people of every mental stripe should find useful ideas in this book.
Rating:  Summary: Overrated, difficult to follow, lack of examples Review: Books on computer programming live or die on the quality of their examples. As every programmer knows, a good example is worth a thousand words. Sadly "Design Patterns" fails miserably in this regard. It suffers from a descriptive overkill that smothers the inherent simplicity of the subject the authors purport to explain. For example, a simple pattern such as "Strategy" is described is such unnecessay detail, that I began to doubt I ever understood it in the first place! For design patterns I was not already familair with, I could not follow them at all. Part of problem is the high-toned, quasi academic style the authors use, with endless citations and qualifications that do anything but explain(Grady Booch is guilty of this too). If you are having trouble with this stuff (and lets face it if Design Patterns is your text book you probably are!), then I can recommend the chapter on OOP in Bruce Eckels book "Thinking in Java" - it helped me make the conceptual leap into OOP. ...
Rating:  Summary: A must-have desk-reference for every OO architect/programmer Review: "Design Patterns" presents a well-ordered catalog of miniature frameworks. Every framework is concisely named, described, and contains concise code examples. In addition, frameworks are accompanied by a thorough discussion of their benefits and drawbacks. Framework names are intuitive and appealing which helps to communicate architectural decisions with other engineers. In short, using this book will clearly take your design decisions to a higher level.
Rating:  Summary: Wonderful, Helpful information Review: Before you buy this, make up your mind that you are going to take a pencil and write all over it. As I was reading this, I constantly was getting new ideas and changing my thoughts on computing. I wrote throughout the pages of this book as I was thinking and it has made the book that much more endearing. A fantastic read!
Rating:  Summary: Excellent description of common patterns Review: This is an excellent book for anyone who is seriously interested in programming or is writing any non-trivial program. Good description of common patterns. A good supplement to your OO Methodology books.
Rating:  Summary: Head banger!! Review: Not absolutely necessary. Unless, of course, you're a serious programmer. Then it's worth the second and third reading.
Rating:  Summary: Get this one! Review: A very good treaty on the subject. A few minor problems here and there in relating a concept, but nothing that can't be figured out with a little effort. And if you don't want to put any effort out to learn, consider going into another field.
|