Features Versus Futures
summary
Argues that every new feature burns optionality (called "futures") so teams must deliberately alternate shipping with refactoring, tests, and design to restore choices; shows a diagram co-refined with Gene Kim and cites how the AI "genie" can turn what used to take 10 people and 2 years into a messy prototype in a week, accelerating "going solid"; recommends juniors spend up to half their time learning and proposes a Git flow with multiple-choice checks per PR; roots practice in ideas from Tidy First and the genie era.
AI-written summary · about
chapters (7)
- 0:00Gene Kim Introduces Kent Beck
- 1:49Nobody Knows
- 7:07Exploristan vs. Extractistan
- 10:14Why Development Slows Down
- 13:45Features vs. Futures
- 19:56Adding Optionality for Teams
- 22:08Closing Thoughts & Resources
related talks
52mBeyond Features
54mTech Truth: Agile Evolution & the Future of SW Engineering
21mDesigning in the age of the 10x engineer
48mIndustry Myth Busting
18mAgile leadership and technical mastery, a harmonious alliance
36mEngineering Intent: Solving the AI Productivity Paradox
01h 03mHow to defeat feature gluttony
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas