Architecture
summary
Tracing Christopher Alexander to software, the talk maps concrete claims: Alexander documents 253 patterns and suggests a community cap of about 7,000 and a four-story limit for livability, insists on 9% parking, and treats patterns as hypotheses. Software history shows 23 patterns in the GoF, Kent Beck’s 50 small‑talk patterns, Fowler’s 42 enterprise patterns, tools like C2 wiki and JUnit, and practices like TCR. Practical claims: buildings and systems cost more to change over time—about 3x commercial 6x residential—so design for continuous adaptation.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 7:50Christopher Alexander’s pattern language
- 13:17Ward Cunningham Kent Beck Smalltalk
- 22:42Defining software architecture
- 25:13Stuart Brand’s lessons for software
- 30:52Key takeaways
- 37:19Q&A
related talks
39mBeyond patterns: Technological systems and the nature of order
40mThe (too) many faces of architecture
41mHow Programs Learn, and What Happens After They're Built
24mThe too many faces of Architecture
01h 01mArchitecture: The Stuff That's Hard to Change
33mSet Design: Putting the "Art" in "Architecture"
45mArchitecture: The Stuff That's Hard to Change
24mBuilding Software Architecture from First Principles