XP In Practise
summary
Flypay moved to pair programming (rotating pairs, ping‑pong tests) and outside‑in TDD across a new microservice and the monolith, co‑committing via a tool they call git do it, running a 10‑minute build CI. Result: far fewer live defects on the microservice, faster ramp for juniors, frequent green builds and daily master commits instead of long‑lived branches. Remaining issues: heavy legacy technical debt slows delivery and requires planned refactor work to restore flow.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:43My first year of university
- 2:42About Flypay
- 3:55Problems in 2015
- 6:12Accidental introduction to XP
- 7:23Microservices
- 8:05Pair Programming
- 12:15High Bus Factor
- 15:20The Extreme Programming Explained
- 15:57Values Principles Practices
- 18:04Values Get A Bad Rep
- 18:40XP Values
- 21:04XP Principles
- 25:09XP Practices
- 29:24Goals
- 35:05Quality
- 40:11Planning
- 41:15Outcomes
- 43:36Technical Debt
- 43:51Questions
related talks
25mProgramming to the extreme
01h 54mPair Programming & Test Driven Development done right
10mBeyond “try harder”: Effective strategies to tackle bugs
36mHow programmers & testers can be productive
52mTesting Microservices
41mShift Left, Shift Right and Improve the Centre
54mDay 2 Ask the Speaker
49mThe Whole Team Approach to Testing in Continuous Delivery