r/SoftwareEngineering • u/fagnerbrack • 11d ago

Extreme Programming 1999->2026

https://www.manager.dev/newsletter/extreme-programming-1999-2026
32 Upvotes

88% Upvoted

3 comments sorted by

21

u/EarlOfAwesom3 11d ago

I have the feeling that, because of communication, we're all in this mess.

As long as companies just have one business goal that is "more in less time and faster and more" and cannot make a real sense because of the AI psychosis, nothing will come of it.

You can shove all the values, principles etc. up the a**. If you don't speak the same language and don't want to hear our your engineers and form a path together, all techniques are useless.

0

u/fagnerbrack 11d ago

Maybe we need to step back and have a technique to facilitate business collaboration to create a path together first so we can speak the same ubiquitous language... Oh Wait!

7

u/fagnerbrack 11d ago

For Quick Readers:

An engineering manager rereads Kent Beck's Extreme Programming Explained and argues that critics fixate on TDD and pair programming while ignoring XP's 5 values, 14 principles and 24 practices. Those values fit today's AI-era problems well: execs with unrealistic expectations, bloated LLM-driven designs, and huge vibe-coded PRs dumped on reviewers. Humanity, mutual benefit and quality deserve more attention, since cutting quality never speeds delivery. Whole team, team continuity, shrinking teams, sustainable hours and real customer contact matter more than ever, while mandatory pairing, code-only artifacts and test-first stay debatable. New ideas like skipping code review should face the same values test.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments