Design Patterns: Elements of Reusable Object-Oriented Software

Comments

1. Anonymous says:

   August 1, 2010 at 2:13 am

   advice if you must read this book

   start on page 81

   When I was in Junior High, there was a teacher whose punishment for chewing gum was to write a 10 page essay on the benefits of chewing gum. I’ll tell you I never chewed gum. Can you imagine how much you have to pad the writing to get 10 pages.
   Rating: 1 / 5
2. A_2007_reader says:

   August 1, 2010 at 4:40 am

   This book is overrated, but it does have utility in bringing to your attention design patterns –which should be obvious to any good programmer–such as the Singleton (object only capable of instantiation once).

   Why do I say obvious? Because any programmer worth their salt will over time develop their own home-grown library of patterns and exemplars to reuse. This book merely calls attention to this habit.

   Also, as other reviewers have pointed out, the text is too generic and abstract, unless you’re into that. Donald Knuth anybody?

   Plus the book is too expensive–if you must, buy it used like I plan to. That’s right, I haven’t read it yet. But I know enough just reading these reviews; sometimes you CAN judge a book by the cover. I am over the age of 13, yes.
   Rating: 2 / 5
3. Anonymous says:

   August 1, 2010 at 6:34 am

   This book serve mostly as historical note. In its time pepole use to think that “the answer” is OOP/OOD. If this book prove anything is that OOP/OOD is NOT the answer. For begginer this book is usless since they do not have the knowlage to read it and evaluate it ideas. For experience programmers this book may serve to prove that in some implemention they were using some ideas that other were using. For those with experience that realy find something new here then I think it only time for them to realized that they are very poor designers. You see in C++ you have many tools to use (and OOP is only one). This book seem to be writing by people who start to program in programming laguages that force you to use object – such as smalltalk. C++ is much more then that and now we know (I realy hope that those who are using C++ know) that OOP is just anther thing to use and not the most important one. Anther problem is that it may lead people to use those patterns in much the same way as OOP – seeing pattenrs everywhere (like many programmer who using OOP see object everywhere). Anther problem is that it like those books about “how to succeed in life in 10 steps”. Well like there is no magic in being successfull (you can’t realy learn how to become one) there is no way in becoming good designer. If you don’t know how to design system, no book can save you. Designing good software is like art, if you don’t have the gift you cannot do it – and ideas from architecture are the worst to take from. When you designing a system, look in the system that you are building for ideas and not in a book that try to solve problems that are not even there. By the way for Java/C# programmers it maybe more usefull (beacuse those lagauges only support OOP). If you are C++ programmer then learn the laguage realy well (there’s much to learn), this is the only thing that will realy help you.
   Rating: 2 / 5
4. nader says:

   August 1, 2010 at 8:13 am

   we are in the women ready clothes production line and we are looking for a supplier of women clothes fashion design program, please advice the ability of providing such program
   Rating: 4 / 5
5. Anonymous says:

   August 1, 2010 at 9:17 am

   I was really surprised that the book didn’t even has a mention of java.It makes a difference to study OOP design with C++ and java.Since inheritence is more stressed in C++ and Contracts in java.So I couldn’t really view the patterns in contracts(java) point of view and the book should have mentioned more on polymorphism in patterns.Here are some books I felt really nice about 1)Java Design –PeterCoad 2)Taming Java Thread –Alen I Holub
   Rating: 3 / 5