am 27. Juli 1999
I am a software development consultant and trainer specializing in design patterns (to give you some perspective). Design patterns are the translation of Christopher's work to software development and involves finding recurring patterns in software development (forgive me for the oversimplified definition). This book has given me incredible insights into building software in ways previously beyond my skills. However, to be honest, I think I may appreciate the esthetics of the book even more. It is so enjoyable to read. I recommend this book to my students, associates and friends all the time and I get many, many "thank you"s for doing so. A note about reading it. Christopher recommends reading the italicized sections if you don't have time to read the whole book as opposed to just reading the first few chapters. This gives you a sense of the entire book as opposed to only the first few chapters in detail. I suggest reading the book through this way first anyway (italicized sections only), and then going back and reading the entire thing. It will take a couple of hours, but then when you go back and read it normally, you will understand and enjoy it much better.
am 2. Mai 2000
This is the book that set the whole software patterns movement in motion. It's a great read. It made me realize how the builder blew it when they made my house. One small design change, the house is 1 ft too narrow makes it impossible to put a screen door on the front door. It made them build a extra platform which causes people to fall down into the living room.
On the other hand, if I was building a building I'd use his visualization techniques before I drew plans. But I wouldn't use this technique to actually construct a building. It would triple the cost. (The essence is to build it as you need it.)
On the other hand he explains why swiss barns look "alike" without the need for a design review committee. (Or barns in general.)
As for software, Design patterns give programmers a way to talk about problems and solutions without talking about code. Its a great idea and I use software patterns all the time. (Get the GOF book for actual software patterns.) Read this one to understand how they came onto this idea.
am 28. Dezember 1999
This book is maybe more popular with computer guys than with architecture people, but it's applicable to all sorts of fields. It's about how you construct a design given a problem and a set of forces acting upon it. I have long worked this way in computing, but since reading the book I have been applying the same techniques to designing the garden in my back yard. I'm sure there's lots more I need to know about design, but I am feeling inspired and confident.
am 28. März 1997
It is amazing how a book that propounds revolutionary
architectural theory has stirred up the computer software
industry. This deeply philosophical book, which is
very practical and rigorous, lays the foundation for
developing "pattern languages".
The book is all about a common language that can be shared to build
artifacts that are alive. It stresses that a design should always
concentrate on the "whole" and not on assembling parts. It also
shows the power of distributed processing, if you will, as against
All the great principles have one thing in common. They are
simple. And, after one realizes such a simple but profound principle, one
can not stop wondering how one survived without it's knowledge. This book gives
feeling. If you are involved in architecture of any sort- buildings, software,
organization or even politics- this book is a must for you.
am 28. Oktober 1998
I bought it because it had been referenced all over the place by computer related authors.
It talks about alot of things that make a lot of sense. Discusses things in their very essence, very zen-like.
Apart from being educational, the book is original, interesting and thought provoking, like any good book one has to read it more than once to fully understand it.
Its one of the best book I have ever read.
am 24. August 1998
This book needs plenty of reading, as it is full of ideas and images that slowly come together to form a whole. It describes "the quality with no name" that make some buildings come "alive" and be wonderful to live in. It is this same quality that makes nature so appealing. The quality is formed from patterns - the second book in the trilogy "A Pattern Language" describes a large number of patterns for architecture in detail.
It is my current opinion that when the "quality without a name" is present in a human relationship it is called "love". If I am right, then in a way this book answers the eternal question "what is love?". Powerful eh?
[I discovered this book following a recommendation of "A Pattern Language" on an object-oriented computing course. The power of patterns in computer software is only starting to be realised]