The Lost Art of Software Design
summary
Many teams stop at vague whiteboard sketches that score “7 out of 10” in workshops and then rush to code, which produces brittle systems and surprise rework. A lightweight upfront design that produces a system context diagram and a container diagram (using the C4 model) exposes tech choices, shows whether AWS Lambdas+DynamoDB designs are needlessly complex, surfaces risks via riskawing.com, and captures decisions with architecture decision records so the starting point actually works.
AI-written summary · about
chapters (9)
- 0:00The state of software design
- 2:46Architecture workshops
- 6:33The case for upfront design
- 10:56Modularity and leadership
- 17:56Communication and diagrams
- 23:58Avoiding superficial design
- 29:27Making technology decisions
- 36:01The C4 model approach
- 44:20Managing risk and closing
related talks
41mThe lost art of software design
30m5 Things Every Developer Should Know about Software Architecture
02mDesign after Agile: How to Succeed by Trying Less
45mFive things every developer should know about software architecture
45mFive things every developer should know about software architecture
53mSoftware Design: Beyond Boxes & Lines
48mDown the Ivory Tower towards Agile Architecture
25mFrom Requirements to Reality: How Solutions Architects Think, Build & Decide