The Philosophy of Architecture
summary
Argues that software architecture defaults to a positivist, circuit-board model that collapses under change — Blockbuster refuses to adapt, asks for an 18‑month rework and goes bankrupt — and proposes a concrete unit called residue to capture time, change and uncertainty. Replaces correctness with criticality, substance with process, and recommends using random simulation (throwing many hypothetical requirements) plus repeated “architectural walks” to get statistically meaningful designs rather than pretending static diagrams are reality.
AI-written summary · about
chapters (13)
- 0:00Philosophy and architecture intro
- 2:16Theory versus practice gap
- 7:33Theory versus reality
- 10:03Philosophy for assumptions
- 13:57Paradigm shifts in engineering
- 17:27Essence vs appearance in design
- 24:51Models obscure reality
- 28:01Escaping complexity trap
- 32:54Process philosophy in architecture
- 36:04Criticality over correctness
- 40:40Linear vs lateral thinking
- 41:46Architectural responsibility
- 43:10Conclusion
related talks
37mArchitecting for Tomorrow: A Pragmatic Perspective
59mDeliberate Architecture
49mWhy software architects fail: and what to do about it
48mArchitecture: The Stuff That's Hard to Change
46mTHE too MANY FACES OF ARCHITECTURE
44mDeliberate Architecture
43mSoftware Architecture, Design Thinking & Knowledge Flow
37mSoftware Architecture for Humans!