Improving Software Flow
summary
Applies the Five Ideals (locality and simplicity; focus, flow, joy; improvement of daily work; psychological safety; customer focus) to concrete engineering changes: use modular services, event-driven async wiring, and an immutable event log to confine failures and invert 23-call hot paths into two synchronous hops (Walmart example) saving tens of millions; run blameless postmortems (Google App Engine 8‑hour outage → 10× fewer reliability issues); invest in continuous delivery (eBay velocity: deployment freq 5×, lead time 5×, change‑failure rate and MTTR 3× improvements, doubled team output).
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:16Background
- 2:49Modular Services
- 4:19Orthogonal Domain Logic • Stateless domain logic
- 6:13Event-Driven
- 7:37Immutable Log
- 10:01Embrace Asynchrony
- 12:37Walmart Item Availability
- 20:41Maker vs Manager Schedule
- 24:27Vicious Cycle of Technical Debt
- 24:55Virtuous Cycle of Investment
- 25:37Continuous Testing
- 27:29Test-Driven Development
- 31:10Use Common Currency
- 32:16Improvement Budget
- 33:25Psychological Safety
- 40:25App Engine Reliability Fixit
- 43:34Business Outcomes
- 44:37Engineering Discipline
related talks
47mImproving Software Flow
46mImproving Software Flow
30mLead Times and Psychological Safety within the Five Ideals
46mAgility and Architecture Together – Enabling a Fast Flow of Change
27mOptimizing the engineering value stream
31mImproving engineering effectiveness: A journey for the entire organization
29mFlow Engineering - boost velocity, quality & happiness
39mMob Programming and the Power of Flow