Deliberate Architecture
summary
Argument: software architecture must be chosen to satisfy measurable quality attributes and constraints rather than follow fashion. Uses the Gartner hype cycle and control‑theory analogies to show qualities are emergent over months and years, not delivered by sprint‑level feature pumps. Cites a surprising 3.5 year half‑life for developer turnover, warns that choosing the wrong style (an observed microservice deployment) produces appalling latency and poor usability, and recommends designing, monitoring and planning for qualities up front.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 6:22Fashion
- 9:19Visual Marketing
- 11:03Gartner Hype Cycle
- 15:34My Hype Cycle
- 21:19Biases
- 25:29Software Architects
- 26:39Software Qualities
- 29:43Tradeoffs
- 29:58Grady Booch
- 30:45My background
- 31:24Incident forces
- 33:24Functions
- 33:54Qualities
- 35:50Nonfunctional requirements
- 37:25Features
- 42:07Emergent vs Nonlinear
- 43:06Agile Process
- 43:58Emergent Qualities
- 45:13Control Theory
- 46:13Software Architecture
- 47:53Agile Feature ISM
- 49:53Portability
- 52:31Personal Style
- 52:54Crosscutting
- 53:46Agile Coach Response
- 56:37Stakeholders
- 57:26Architect
- 57:54Advice
related talks
44mDeliberate Architecture
01h 14mDeliberate Architecture
49mCultivating Architecture
46mArchitecture Transformation Challenges
49mWhy software architects fail: and what to do about it
37mSoftware Architecture for Humans!
37mArchitecting for Tomorrow: A Pragmatic Perspective
44mThe Philosophy of Architecture