Extreme Programming

Extreme Programming (XP) is an agile software development methodology introduced by Kent Beck in the late 1990s that takes proven engineering disciplines and turns their dials up to the extreme. If code review is good, review continuously through pair programming; if testing is good, write the tests first; if integration is good, integrate many times a day. The goal is working software that stays responsive to changing requirements right up to the last responsible moment.

• Test-Driven Development - Write a failing test before the code that satisfies it, so behavior is specified and verified as it is built.
• Pair programming - Two engineers at one workstation, giving continuous review, shared context, and fewer defects reaching the branch.
• Continuous integration - Merge and build frequently to surface conflicts and regressions early instead of at a painful end-of-cycle merge.
• Small releases and short iterations - Ship in tight increments so feedback arrives fast and course corrections stay cheap.
• On-site customer and whole-team feedback - Keep the person who knows the requirements close to the work so priorities and acceptance stay clear.

In API practice, XP’s habits are the quiet engine behind reliable API delivery: contract tests and TDD keep an API’s behavior matching its OpenAPI definition, continuous integration gates every change against that contract, and short releases let a provider evolve endpoints without breaking consumers. The methodology predates the agentic turn, but its core bet — tight feedback loops and always-tested, always-integrated code — is exactly what makes an API safe to change quickly, which is what any team shipping and governing APIs at pace still needs today.