ABC of Architecture is an accessible, nontechnical introduction to architectural structure, history, and criticism. Author James F. O'Gormon moves seamlessly from a discussion of the most basic inspiration for architecture (the need for shelter from the elements), to an exploration of space, system, and material, and, finally, to an examination of the language and history of architecture. He shows the nonspecialist how to read a design in plans, sections, and elevations, and how architects, like other artists, make creative use of space and light.
Software Architecture is what Amazon calls “Type 1 Decision”. They are one way doors that are - for all practical purposes - irreversible. Once you build an “event-driven system” based on lambda/serverless technology with a persistent message queue (say, Kafka), you will have to live there. This short book could help incepting the metaphor and finding concrete parallels. It stays true to the principle - “incompetence will show in the use of too many words”.
Code embodies the system, design represents our good faith “digitization” of the system, and architecture is the structural metaphor of the system itself. After you see a house, the very first thing that comes to your mind - “craftsman”, “Bronx Apartments” - is the architecture. Architecture, therefore, offers a shared and common vocabulary that compresses the essence of the system. “That thing sticking out of the roof” is a “chimney”.
ABC…shares how traditional architecture was shaped with the advance in technology. Egyptians built giant monoliths - robust but not resilient. Greeks built post and beam - rectangular large space enclosed by relatively larger mass. Romans added arches and vaults - gave it all “angles”. Industrial revolution introduced steel and reinforced concrete - to achieve a much larger scale, and utilization with huge savings in materials. Extend that metaphor - and you can write in one line of Go what it would take you 100s of lines of assembly language!
Vitruvius framed architecture on a trifecta of function, structure and beauty (Utilitas, Firmitas and Venustas). This Vitruvian triangle, moving through time, creates architectural imprints. The difference between Stonehenge and the Empire State Building is, therefore, basically historical rather than statical. The posts of the latter are made of steel, and not of stones.
One thing from the book - “The arch shows technological advance over post and lintel because it avoids the limitations of the one available stone horizontal member by using relatively small stones in combination to achieve relatively large spans….and it is easier to man-handle than a large lintel”.
Could very well be how larger monolithic codebases were broken into more manageable “microservices” each of which was far easier to handle!
As the title says, it is the A, B, and C of architecture. I guess I was also looking for the D, E, and F because it left me wanting.
The three aspects the book covers are Utilitas, Firmitas, and Venustas which are Function, Structure, and Beauty respectively. All three aspects are present in any project and each determined by the others.
Function is from the Client, structure is for the Builder, and beauty is the realm of the Architect, but all three aspects are interdependent.
I was hoping to learn more about symmetry, scale, proportion, rhythm, shape, massing, textures and all the other elements that contribute to the function , structure, and beauty of a building. So I guess I'll keep looking.
This is a book I wish I would have read 10 years ago. It is very basic; perfect for someone considering or about to start a program in architecture. It lays out some fundamental vocabulary and ways of thinking about spatial relations. Building off of the ancient Roman architect Vitruvius' three components of building (Utilitas, Firmitas, and Venustas), O'Gorman organizes his book to explore the three fundamental interdependent components of architecture. The ABCs of architecture are function, structure, and beauty which are best depicted respectively in plan, section, and elevation with the prime determinants being given by the client, constructor/engineer, and architect. This theme of keeping things simple and clear with a consistent three-part division of architecture works quite well for an introductory overview of what gets talked about in architecture school, theory, and practice. By no means is it exhaustive, however, and I believe--having completed a Bachelor's degree in Architecture at UC Berkeley, that most of this stuff gets covered very quickly and almost implicitly within a month of the program. But like I said, with a nervous anxiety of being just about to start architecture school, I think this would be the perfect read to instill a bit of confidence and basic vocabulary to get one started. There are a few overly-simplified divisions (particularly classical vs. picturesque) and obvious omissions (a discussion of modernism for example), but otherwise it is fairly beautiful in its simple organization and execution.
Excellent overview. I loved the illustrations. It was great until the last chapter on vocabulary. He should have skipped that. I didn't really get the architectural puns (if that is what those were) and without illustrations it was useless. I didn't finish that chapter. I will get my vocabulary from a book I have already picked up that has illustrations.
One more thing. I was unsure what the author's attitude toward Frank Lloyd Wright was. He made a couple of comments about FLW and I didn't understand them. Did he think FLW was over rated or under rated?
Although repetitive, accessible enough to understand as a novice to this field with sufficient content to stay engaged. Seemed to be more a teaching perspective initially then fell into almost stream of consciousness description of concepts in architecture. Drawings were helpful in understanding written concepts/definitions.