The reading room · Digna Legi
Extreme Programming 1999->2026
/100
80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.
Evidence-reviewed score based on available publisher text. The evidence is sampled with gaps, so the full structure and possible repetition cannot be fully assessed.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 3 min with detail
Why read this
Extreme Programming still matters as values, principles, and practices for judging software work under AI-era pressure.
AI brief · Checked against source text
The main idea
The central claim is that Extreme Programming remains useful because it is not just pair programming or test-first development: its values define direction, practices make values observable, and principles translate between the two. The author uses this structure to assess modern AI-era engineering pressures: architecture bloat, oversized generated pull requests, review bottlenecks, eroded role boundaries, and executive expectations that software should now be easy.
Some background helpful. Software-team terms: pull requests, automated tests, deployment, large language models, and agile methods.
Go a little deeper
XP is presented as a translation system
The author’s most durable move is separating values, principles, and practices rather than defending individual rituals. Values such as communication and simplicity are too vague to govern behavior alone; practices are concrete but can become context-blind; principles explain how to adapt practices without abandoning the value. That framing lets XP survive disagreement over test-first work or pair programming.
AI makes simplicity harder, not easier
The text argues that cheaper code generation can increase design risk because teams can now create more structure faster than they can justify it. The danger is not only bad code, but inflated scope during planning and architectures that look impressive while outgrowing the actual need. In this reading, simplicity becomes a discipline against abundance rather than scarcity.
Mutual benefit attacks review dumping
The author uses XP’s mutual benefit principle to criticize work that shifts pain downstream: unreadable AI-written messages, huge generated pull requests, and documentation that burdens only a future maintainer. The useful distinction is that collaboration is not proven by producing artifacts for others; the activity should benefit both the producer and the receiver now, or it corrodes teamwork.
Team continuity is treated as productive memory
The piece rejects treating engineers as interchangeable capacity. Stable teams matter because part of the software system is relational: people build shared knowledge, working relationships, and a history of accomplishing things together. The author still notes a tension with XP’s shrinking-teams practice, where growing capability should eventually free people for new teams, but he would start smaller rather than casually break strong teams.
A case from the article
Weekly customer calls reduce proxy distance
The author describes starting one-on-one customer calls with engineers and making some of them weekly. This falls short of XP’s stronger practice of making a real customer part of the team, but it illustrates the same mechanism: shortening the chain between builders and affected users so the team learns from actual needs instead of filtered assumptions.
How the case is made
The case is made through first-person rereading, quoted XP concepts, and the author’s observations of engineering management under AI adoption.
Where the idea has limits
Do not treat the author’s broad claims about AI pressure, architecture bloat, or review burden as measured prevalence claims; the text supports them as experienced patterns and interpretive judgments.
A question to take away · from Digna Legi
Which of your team’s current practices actually prove its stated values, and which merely borrow the vocabulary?
What the original adds
The original contains a fuller categorized pass through XP practices, including which the author sees as more critical, controversial, common sense, or changed by remote work and LLMs.
About this brief
AI-written, then separately checked for source support, useful detail and clarity. The author’s claims and our editorial question are kept separate. The original remains the author’s work. How we select and summarise →
How was this brief?
Rate this summary, separately from the author’s article.
Optional. Saved in this browser; shared only if you allow analytics.
How was the original article?
Rate the author’s original after reading it.
Optional. Saved in this browser; shared only if you allow analytics.
Digna legi. Worth reading.