Rating: 
Summary: A Powerful Way of Thinking
Review: Alexander's "A Timeless Way of Building" is a philosophical treatise which has informed my thinking profoundly. Without any formal training or interest in architecture, per se, this book has opened a world of awe for me. Awe of language, of systems, of people. It almost reads as a spiritual text - but with the credibility afforded only to those who clearly address specific content (architecture and city planning, in this case). Alexander's writing is clean and precise. His ideas are powerful, they are more true today than in '79 and in more domains than architecture. I recommend this to anyone who is curious about how systems work.
Rating:
Summary: A Powerful Way of Thinking
Review: Alexander's "A Timeless Way of Building" is a philosophical treatise which has informed my thinking profoundly. Without any formal training or interest in architecture, per se, this book has opened a world of awe for me. Awe of language, of systems, of people. It almost reads as a spiritual text - but with the credibility afforded only to those who clearly address specific content (architecture and city planning, in this case). Alexander's writing is clean and precise. His ideas are powerful, they are more true today than in '79 and in more domains than architecture. I recommend this to anyone who is curious about how systems work.
Rating:
Summary: Only book in both my top 5 personal & professional list
Review: 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.
Rating:
Summary: absolutely brilliant
Review: 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.
Rating:
Summary: this book blew me away
Review: I bought this book because i am about to build a house. Coincidentally, i am also a senior software engineer and very familiar with design patterns in my field - i use them every day. They work very well for programming computers. This book, however, literally takes the concept of living patterns to architecture, and, by extension of the act of creation, to life itself. At the same time as being a great philosophical read, it's also a handy guide to building a house. Bonus points for the author: The book can be read in 15 minutes (reading the "detailed table of contents"), in one hour (reading only the headlines), or in the full. These modes of reading the book come from the author's emphasis of the whole over the parts, e.g. the whole is more than the sum of its parts. I am not entirely sure that, as the author promises, i will now be able to go and build a house, without drawing a plan... but that this idealistic goal is in practice hard to attain does not make the incredibly deep insights in this book any less true or any less practical. Like another reader said - the book changed the way i think about... everything! Patterns as described in this book are far more refined than anything we use in computer science, and that he sees them in a much broader light. The central grandiose idea is the one of complete interconnectedness of the patterns - the whole, which is more than the sum of its parts.
Rating: 
Summary: Interesting Ideas, Poetic Language
Review: I come to this book as a designer, as a technology professional, as a manager, and as a person who has always been interested in gaining an understanding of the patterns and systems governing our universe. The book is organized into three sections, I'll summarize each of them for you. The Quality The author postulates a Quality without a Name. "The fact that this quality cannot be named does not mean that it is vague or imprecise... I shall try to show you now, why words can never capture it, by circling around it, through the medium of a half a dozen words." These words are "Alive" "Whole" "Comfortable" "Free" "Exact" "Egoless" "Eternal." The Quality is related to yet is none of those things. My take on this section is that this Quality Without a Name is very sort of touchy feely. It seems to boil down to trusting your emotions - if something feels good it is good. The Gate In the introduction the author says that there is only one way of building. "There is one timeless way of building... It is... powerful and fundamental... And there is no other way in which a building or a town which lives can possibly be made." The author states that because architects and city planners are removed from the community, unlike the way people once built things, that we've lost this way, this language. He then proposes a Pattern Language, which is the heart of the book (In my humble opinion). A Pattern is a way to identify, build, and share this precies way of making buildings and towns that are alive. "... every pattern we define must be formulated in the form of a rule which establishes a relationship between a context, a system of forces which arises in that context, and a configuration which allows these forces to resolve themselves in that context. "It has the following generic form: Context -> System of forces -> Configuration." If you can define a context, problem, and solution, you have a pattern that can be used to build something, and can be shared by other people. You get to this definition by thinking of a place that is alive, that's comfortable, and focusing on the geography, on the space. What makes it so good? What is the need that this place fills? This is always hard to do: going from the general to the specific or the specific to the general requires a mental leap, and the author provides a some examples of how to do this. How to determine if something has this "Quality Without a Name." Every complex thing (like a flower) is made up of many simple things that are self-sustaining. Any non-sustaining system within the whole will bring the whole down. This is true of buildings and places as well. "Half Hidden Garden", for example, may be made up of "Courtyards Which Live" "Garden Growing Wild" "Terraced Slope" "Fruit Trees" "Sunny Place," etc. You shouldn't even begin to design until you have a complete picture of what the garden will be like by filling in all of the details. This section, I believe, inspired Object Oriented Programming. A "Sunny Place" can be used in other "Half Hidden Gardens" or in an entirely different structure, like a Park. The Way I decided to skim this section, so my summary here will probably miss a few important points. I may go back and read it in more depth at a later date. Here he describes how the language can live, like a genetic code - picked up and modified by people over time so that multiple languages can evolve. He also describes how to put the pattern into action. The idea of a Pattern Language appeals to me, and I like many of the concepts the book puts forward, however I found his tone to be self-congradulatory, and he didn't seem to put much stock in his reader. The tone was very much "My idea is revolutionary, and you must be prepared to recieve it." Many of his arguments are put forth poorly. Either he doesn't describe his premise well, or the logic itself seems flawed. For example, he says that this process is both precise and based on feelings. Reading the book this seems contradictory, but upon later reflection it makes sense. It was just stated poorly. What he's proposing is a way of defining, or pinning down, what about a place makes it feel good. A specific process to define why a you like something, and formula for communicating it. Overall, I felt he could've been a LOT more concise and either made the book smaller, or packed a lot more useful information in. It felt very much like a first draft, and that he was still working through his ideas and not quite prepared to communicate them effectively. Several of the other reviews of this book seem to miss the point, and I take that as further indication that the author was struggling to get his ideas across. The author believes that getting an overview of his concepts is more important than the details, so he arranged the book so you can read the "headlines" quickly to get an overview. For me this was distracting because he changes voice for every paragraph, and the book loses it's narrative flow. I give this book five stars for content, but remove one for the way it was communicated. I suggest it to anyone who is interested in developing a system (these ideas apply to much more than architecture), a taxonomy, a structure, or those with a purely academic interest in the author's ideas. I'm actually anxious to put some of them to use. The second book in this series is called A Pattern Language, and it's 230 or so patterns, ranging from Region to Town to Sunny Area. The third book is The Oregon Experiment, which I believe chronicles the building of a school based on these principles.
Rating:
Summary: The Etymology of Software Architecture
Review: I found this book so mesmerizing that I read it twice. During the first pass, I was surprised that the book was so philosophical and poetic in describing architecture. I expected something more technical. Later during the second pass, my goal was to find derivatives and analogies in software architecture. Based on what I found, I think every software architect would enjoy this book. The writing style that I noticed in my first read of the book made me feel like I was reading an architecture bible. I hesitate to describe the book as religious, but the book's description "the power to make buildings beautiful lies in each of us already" and the description of the word "alive" giving architecture "the quality without a name" triggered an epiphany when recalling that the Bible says "In the beginning God created the heaven and the earth." and, "So God created man in his own image." This is why I'd say this book has a primal, sacred aspect, and this is why we like to build. Additionally, the book especially moved me so my mind's eye was opened to see "alive" patterns and to think about the morphology of architecture filling voids and generating towns. On the second pass of reading, I was struck by this software architecture analogy in the table of contents: "16. Once we have understood how to discover individual patterns which are alive, we may then make a language for ourselves for any building task we face. The structure of the language is created by the network of connections among individual patterns: and the language lives, or not, as a totality, to the degree these patterns form a whole." Could this be the guidebook for designing enterprise software architecture? Obviously this book was the inspiration for the philosophy and vocabulary for software architecture, and I thought some of the following excerpts were noteworthy paradigm shifts. "The patterns are not just patterns of relationships, but patterns of relationships among other smaller patterns, which themselves have still other patterns hooking them together---and we see finally, that the world is entirely made of all these interhooking, interlocking nonmaterial patterns." This sounds like the difference between patterns of software architecture and object-oriented software design patterns. "Each pattern is a three-part rule, which expresses a relation between a certain context, a problem, and a solution." Deja vu for software patterns. "You may be afraid that the design won't work if you take just one pattern at a time...There is no reason to be timid...The order of the language will make sure that it is possible." Likewise in software architecture design, as one design pattern is considered at a time to see how it fits needs into the large picture of design. If this pattern is later deemed to be dead, it can be replaced by an "alive" design pattern.
"Next, several acts of building, each one done to repair and magnify the product of the previous acts, will slowly generate a larger and more complex whole than any single act can generate." This correlates to software refactoring. "It is essential, therefore, that the builder build only from rough drawings: and that he carry out the detailed patterns from the drawings according to the processes given by the pattern language in his mind." When I read this, I thought about the metaphor to the software architect's vision and design. The software architect's design needs to be abstract enough to accommodate change easily, but yet simple enough so software programmers can understand it, finish the detailed component design and build the component to fit the architectural whole.
Rating:
Summary: The Etymology of Software Architecture
Review: I found this book so mesmerizing that I read it twice. During the first pass, I was surprised that the book was so philosophical and poetic in describing architecture. I expected something more technical. Later during the second pass, my goal was to find derivatives and analogies in software architecture. Based on what I found, I think every software architect would enjoy this book. The writing style that I noticed in my first read of the book made me feel like I was reading an architecture bible. I hesitate to describe the book as religious, but the book's description "the power to make buildings beautiful lies in each of us already" and the description of the word "alive" giving architecture "the quality without a name" triggered an epiphany when recalling that the Bible says "In the beginning God created the heaven and the earth." and, "So God created man in his own image." This is why I'd say this book has a primal, sacred aspect, and this is why we like to build. Additionally, the book especially moved me so my mind's eye was opened to see "alive" patterns and to think about the morphology of architecture filling voids and generating towns. On the second pass of reading, I was struck by this software architecture analogy in the table of contents: "16. Once we have understood how to discover individual patterns which are alive, we may then make a language for ourselves for any building task we face. The structure of the language is created by the network of connections among individual patterns: and the language lives, or not, as a totality, to the degree these patterns form a whole." Could this be the guidebook for designing enterprise software architecture? Obviously this book was the inspiration for the philosophy and vocabulary for software architecture, and I thought some of the following excerpts were noteworthy paradigm shifts. "The patterns are not just patterns of relationships, but patterns of relationships among other smaller patterns, which themselves have still other patterns hooking them together---and we see finally, that the world is entirely made of all these interhooking, interlocking nonmaterial patterns." This sounds like the difference between patterns of software architecture and object-oriented software design patterns. "Each pattern is a three-part rule, which expresses a relation between a certain context, a problem, and a solution." Deja vu for software patterns. "You may be afraid that the design won't work if you take just one pattern at a time...There is no reason to be timid...The order of the language will make sure that it is possible." Likewise in software architecture design, as one design pattern is considered at a time to see how it fits needs into the large picture of design. If this pattern is later deemed to be dead, it can be replaced by an "alive" design pattern.
"Next, several acts of building, each one done to repair and magnify the product of the previous acts, will slowly generate a larger and more complex whole than any single act can generate." This correlates to software refactoring. "It is essential, therefore, that the builder build only from rough drawings: and that he carry out the detailed patterns from the drawings according to the processes given by the pattern language in his mind." When I read this, I thought about the metaphor to the software architect's vision and design. The software architect's design needs to be abstract enough to accommodate change easily, but yet simple enough so software programmers can understand it, finish the detailed component design and build the component to fit the architectural whole.
Rating:
Summary: A breathtaking and profound book.
Review: 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
centralized processing.
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 that feeling. If you are involved in architecture of any sort- buildings, software, organization or even politics- this book is a must for you.
Rating:
Summary: Esoteric, Abstract and useful too..
Review: It is the most wonderful book that I have read after reading "the fountainhead" by Ayn Rand.It not only gives you great architectural ideas but generates a kind of euphoria that most books don't.Defenitely the best book on patterns.
| 
