Abort! Abort! Abort! A reversible course of action
summary
Argues for choosing reversible vs irreversible changes: prefer edits that can be rolled back quickly (example: removing a custom operator after finding it used only three times) over sweeping platform swaps that ripple through 10+ layers and take weeks to undo. Uses Babylon Health experience and cost framing (25 iOS engineers losing an hour costs thousands of pounds) to justify an evolutionary approach: run parallel experiments, isolate features or teams, and let successful variants propagate rather than enforcing a single top-down architecture.
AI-written summary · about
chapters (5)
- 0:00Fear of losing control
- 3:35Reversible vs irreversible decisions
- 9:15Evolutionary approach to decisions
- 14:16Independent team experiments
- 15:50Mental health awareness
related talks
54mKeynote – Kent Beck
27mStrategies for making impossible decisions
41mThe big Rewrite
57mStrategic Decision-Making for Tech Leaders and Developers
26mIndecisions Are Not All Bad
46mArchitecture Transformation Challenges
36m"Engineering to embrace change" Or "How clumsy engineering can lead to powerful research – Part II"
16mBetter Stories, Better Software