How Technical Debt Can Kill Your Business. How F1 Teams Crack Technical Debt
summary
Four concrete failure/success contrasts: a fintech duplicates whole codebases per country and multiplies maintenance cost until growth stalls, while an F1 team decouples telemetry and swaps ECUs at runtime; a betting operator splits feature and bug teams and collapses, while F1 keeps full-lifecycle teams, pair programming and TDD; long 20‑year codebases are tamed by weekly releases, automated tests, trunk‑based development and one‑click rollback plus a two‑phase release for breaking changes, delivering faster and safer.
AI-written summary · about
chapters (12)
- 0:00Start
- 4:53Definition of Technical Debt
- 9:38Electronic Engine Control Units
- 10:58Drive by Wire
- 20:39Race Engineers
- 43:59Business and Technology Collaboration and Trust
- 46:36Tips in Order To Develop Technical Practices
- 59:36Training the Developers
- 1:01:05Success Story
- 1:13:39How Do You Know to What Previous State To Roll Back
- 1:15:31Two-Phase Release
- 1:17:13Continuous Refactoring
related talks
28mTechnical Debt: Why it'll ruin your software
34mThe Technical Debt Trap
35mTechnical Debt. A guide for developers and IT managers
26mTech debt as innovation, reframing this forever problem as an opportunity
31mTech Debt: Leverage for velocity acceleration
01h 01mThe Technical Debt Prevention Clinic
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
01h 12mBuilding a Technical Credibility to Fight Technical Debt