Predictable is better than fast
summary
Claim: making teams and systems predictable beats chasing raw speed because predictable work reduces cross-team churn and long-term delays. Evidence: shipping physical products requires months of lead time so software dates must be reliable; an AI-generated web form and copy that looked fine but failed because it skipped review steps shows tools can speed things but break coordination; practical fixes include feature flags for safe merges and CMS controls to shift work out of developer release cycles, all of which are implemented and effective.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:08AI not miracle cure for speed
- 2:31Hidden costs of late/early delivery
- 5:58Feature flags challenges
- 7:01Predictability pillar
- 8:25Skipping steps with AI fails
- 9:50Root causes of unpredictability
- 10:51Conclusion and call to prioritize predictability
related talks
29mEconomies of Speed
45m"Moving Fast at Scale"
51mThe astonishing value of speed
01h 21mTradeoffs in the Software Workflow
23mThe Cost of Speed: Rethinking "Move Fast" in DevOps
30mMoving Fast At Scale
22mFail Fast, Fail Often - Make Safety a Prerequisite for your Team
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas