Heavybit Podcasts Ep. #2, Features and Futures with Kent Beck
9 snips
Apr 1, 2026 
Kent Beck, veteran software engineer who created JUnit and helped popularize TDD and Extreme Programming. He discusses progressive delivery, reversible releases, and feature flags. He explores AI-assisted coding and augmented development. He talks about balancing new features with long-term options and the role of observability and testing in production.
AI Snips
Chapters
Books
Transcript
Episode notes
Implementation Is Not A Magic Black Box
- Treat implementation as visible, testable work rather than a magic black box; incentives otherwise make programmers claim finished prematurely.
- Kent contrasts superficial Agile rituals with Extreme Programming practices that force responsibility and reliability in implementation.
Bring People Together To Share Responsibility
- Favor bringing people together to share context instead of rigidly separating roles; collaboration preserves information and responsibility.
- Use XP rituals and social structures to prevent single-person knowledge silos and promote shared ownership.
Intentionally Allocate Work Between Features And Futures
- Split investment between features and futures deliberately instead of defaulting to easy-to-count features.
- Use a dynamic ratio (50-50, 70-30, etc.) based on relative value, avoiding sunk-cost bias toward visible feature counts.
