We're Good At Writing Software [Keynote]
summary
Asserts that known practices from the last 25 years make steady, low‑bug delivery possible and then names the concrete plumbing: automated tests that describe behavior not structure, incremental design and frequent tidy ups, tiny experiments instead of giant bets, and putting a customer on the team so demos happen — often frequent demos every Friday. Gives measurable goals: teams of ~10–30 hit six months without a bug and sustain predictable delivery by planning half and using magic‑circle work cycles.
AI-written summary · about
chapters (19)
- 0:00From desert to forest
- 3:14Observing the software forest
- 5:23Six months without bugs
- 8:11Incremental design
- 10:26Experimentation over perfection
- 14:00More features, fewer bugs
- 15:03Customer presence in dev
- 17:32Skills and learning
- 19:40Plan half the work
- 23:16Balancing roots and fruits
- 24:21Frequent demos
- 27:38Focused work cycles
- 30:49Rest and reflection
- 33:22Team-level practices
- 34:22Breaking team barriers
- 37:15Shared goals and alignment
- 41:11Step by step to forest
- 43:01Building community
- 46:58Choosing forest over desert
