The lost art of software design
summary
Argues that some upfront design is necessary to avoid costly refactors, recommends drafting a system context diagram and a container diagram (C4 model) as a sufficient starting point, naming significant tech choices (databases, frameworks) and recording them as architecture decision records. Advises proving risky assumptions with prototypes, spikes and “risk storming”, using fitness functions and threat models to validate the design. Reports many teams produce ambiguous whiteboard diagrams (workshop examples often score ~7/10) and overuse microservices without evidence.
AI-written summary · about
chapters (10)
- 0:00Introduction to lost art
- 3:56About the speaker
- 6:23Upfront design necessity
- 12:04Evolutionary design approach
- 15:55Diagrams and UML critique
- 23:12Hype-driven architecture pitfalls
- 26:00Significant design decisions
- 29:49C4 model for architecture
- 33:21Agile architecture techniques
- 37:55Closing and Q&A
related talks
52mThe Lost Art of Software Design
45mFive things every developer should know about software architecture
30m5 Things Every Developer Should Know about Software Architecture
45mFive things every developer should know about software architecture
02mDesign after Agile: How to Succeed by Trying Less
47mMaking architecture decisions, the Agile Way
25mThinking Architecturally
57mSoftware Architecture: The Hard Parts