Like Software, Buildings Are Made Of People
summary
Argues that buildings and software share concrete engineering problems not vague metaphors: construction enforces dependency management with components deployed in order and mandatory inspections and QA that prevent shipping until tests pass, while software relies on refactor instead of renovate, reusable modules, and ad hoc third‑party parts. Shows construction-grade observability and auditing tools, ties recurring cost overruns and failed projects to perverse incentives, and demonstrates where code‑era practices succeed or break when applied to physical projects.
AI-written summary · about
chapters (4)
- 0:00Start
- 3:02THAT'S A LOAD BEARING CLASS
- 3:18DOCUMENTATION IS NO SUBSTITUTE FOR UNDERSTANDING
- 4:49INCENTIVES MATTER
related talks
33mSet Design: Putting the "Art" in "Architecture"
24mThe too many faces of Architecture
40mThe (too) many faces of architecture
41mHow Programs Learn, and What Happens After They're Built
50mCoevolution of Architecture & Code - Closing The Gap
45mArchitecture: The Stuff That's Hard to Change
45mSoftware Architecture for Humans!
01h 02mThinking Like an Architect