Keynote: Software Design in the 21st Century
summary
Argues agile’s core is tolerating changing requirements, team autonomy and continual design work, not ceremonies; gives the agile fluency progression (management practices → technical practices → metrics/AB testing), claims many teams take years to reach the second level but that level drastically lowers defects — one team fixes production defects same day via continuous delivery and automated tests; prescribes tiny-step refactoring (red green refactor), frequent local commits on green, avoid long feature branches, and frames refactoring as the economic way to preserve velocity (design stamina hypothesis).
AI-written summary · about
chapters (16)
- 0:00Essence of agile
- 1:14Agile vs plan-driven
- 3:24Handling change
- 5:58Team autonomy
- 8:56Evolution of agile
- 12:24The fluency model
- 14:51Level one fluency
- 16:18Technical practices
- 20:06Advanced fluency
- 23:27Introduction to refactoring
- 25:00Refactoring techniques
- 28:14Comprehension refactoring
- 30:12Preparatory refactoring
- 32:40Continuous refactoring
- 36:12Refactoring vs rewriting
- 38:25Economic argument
related talks
53mKeynote: Tidy First? A Daily Exercise in Empirical Design
45mYou can't be agile when you're fighting your code
48mAgility and Architecture Together – Enabling a Fast Flow of Change
36mFrom Software to Systems: Modern Agility
39mAgility in Software Architecture
38mAgile Architecture
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
59mAgile Engineering: The Hard Parts