- Series: Center for Environmental Structure (Book 1)
- Hardcover: 552 pages
- Publisher: Oxford University Press (1979)
- Language: English
- ISBN-10: 0195024028
- ISBN-13: 978-0195024029
- Product Dimensions: 8 x 1.2 x 5.7 inches
- Shipping Weight: 1.4 pounds (View shipping rates and policies)
- Average Customer Review: 59 customer reviews
- Amazon Best Sellers Rank: #81,870 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
The Timeless Way of Building
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
"Excellent text for architectural theory and design--a must for design students."--Brad Grant, California Polytechnic State University
About the Author
Christopher Alexander is a builder, craftsman, general contractor, architect, painter, and teacher. He taught from 1963 to 2002 as Professor of Architecture at the University of California, Berkeley, and is now Professor Emeritus. He has spent his life running construction projects, experimenting with new building methods and materials, and crafting carefully articulated buildings--all to advance the idea that people can build environments in which they will thrive.
Acting on his deeply-held conviction that, as a society, we must recover the means by which we can build and maintain healthy living environments, he has lived and worked in many cultures, and built buildings all over the world.
Making neighborhoods, building-complexes, building, balustrades, columns, ceilings, windows, tiles, ornaments, models and mockups, paintings, furniture, castings and carvings--all this has been his passion, and is the cornerstone from which his paradigm-changing principles have been derived.
Browse award-winning titles. See more
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
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.