The Philosophy of Architecture
summary
A PhD in complexity science reframes software architecture as a philosophical problem: default logical positivism makes architects model people as circuit boards, which causes the architect's paradox where better programming worsens handling of change. The alternative is emergentism and walking the system repeatedly to gather pragmatic knowledge, aiming for criticality vs correctness. Practical tools shown include residue as a unit of architecture, random simulation and complexity-science techniques, plus a new book outlining how to design for time, change and uncertainty.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 7:53Defining software architecture
- 11:25Engineering paradigm limits
- 18:06Architect’s paradox
- 23:23Positivism vs interpretivism
- 29:21Architect’s matrix
- 32:11Emergentism and complexity
- 37:27Architects’ knowledge
- 40:00Architect’s critical role
- 43:12Philosophy for better architecture
- 46:05Conclusion
related talks
37mArchitecting for Tomorrow: A Pragmatic Perspective
56mEssential Architectural Thinking – Why, What, How, When and How Much?
51mSoftware Architecture for Humans!
46mTHE too MANY FACES OF ARCHITECTURE
02mThe architecture of uncertainty
48mArchitecture: The Stuff That's Hard to Change
50mKEYNOTE: Residuality Theory in Software Architecture
46mHow does the architect know?