
Creating Extreme Programming

TDD, AI agents and coding with Kent Beck
Topic 5 of 11
Published Jun 11, 2025 · Clip 26:20–35:26 (9:05)
Kent describes the origin of Extreme Programming: as a technical consultant he noticed huge leverage in team context and furniture arrangement, wrote the first xUnit-style testing framework (SUnit) in a panic for a fintech client, then at a floundering Chrysler project cranked everything that worked up to 11. He named it extreme to pick a word Grady Booch would never say and rode the dot-com era's desperate need for predictability. He explains XP's essence - slicing time finely across figuring out what to do, structure, implementation, and validation - and tells the story showing pairing eliminated all production defects found by the customer, while stressing XP is empirical, not mandated.