A revisit of Kent Beck's Extreme Programming Explained, thirty years after XP's creation, arguing its five values, fourteen principles, and 24-26 practices remain relevant amid AI-driven software development. The piece breaks practices into 'more critical than ever' (whole team, team continuity, energized work, real customer involvement), 'controversial' (pair programming, code-and-tests-only, test-first programming), 'common sense', and 'still relevant?' categories, weaving in commentary on AI slop, vibe-coded PRs, engineering burnout, and leadership communication gaps. Includes a sponsored mention of an AI coding analytics tool called Weave.
Table of contents
So what IS extreme programming?The 5 ValuesThe 3 critical Principles24 practices across 4 categoriesFinal wordsWhat I enjoyed reading this weekQuestions this post answers
What are the five core values of extreme programming according to Kent Beck's book?
The five values are communication, simplicity, feedback, courage, and respect. Communication addresses gaps between leadership and engineers; simplicity asks what is the simplest thing that could possibly work; feedback stresses rapid iteration; courage empowers pushing back on unreasonable demands; and respect underpins genuine teamwork, without which the other values fail. daily.dev surfaces engineering culture discussions for managers weighing how these values apply today.
Which extreme programming practices are considered most controversial today?
Pair programming, code-and-tests-only, incremental design, and test-first programming are flagged as the most contested. The sticking point is usually the word 'all' or 'only' — writing every production line in pairs or maintaining zero documentation is seen as impractical, especially now that engineers often work solo alongside LLMs instead of a human partner. daily.dev helps teams debate which XP practices still hold up when adapting workflows around AI tools.
541.1K Impressions12 Comments