Software Design: Beyond Boxes & Lines
summary
Claims that software design is participatory sense making and that the single leverage point is a shared language drive concrete practices: map capabilities with a value‑stream/worldly map, form stream‑aligned product teams owning deployable units, use bounded contexts and anti‑corruption layers, apply hexagonal architecture and feature flags, and instrument observability (Honeycomb style) to learn from production. The example builds a “Captain R” creature to show a new stereo became a required capability, pushed a team into Genesis, and proved faster iteration with less rework.
AI-written summary · about
chapters (11)
- 0:00Software design intro
- 1:11Fantasy creature exercise
- 8:39Business capability mapping
- 17:17Product teams and cognitive load
- 23:19Bounded contexts and DDD
- 31:08Shared language in design
- 35:25Philosophy of shared models
- 42:12Empathy and inclusion
- 44:40Q&A: Bias in sense making
- 47:52Q&A: Ethics in design
- 50:00Q&A: Practical steps
