For YAGNI listeners

My engineering team at ZAR builds with coding agents all day. The process most teams inherited assumes typing is the expensive part, and it stopped being expensive.

Impatient Programming is the process we arrived at. It takes the twenty-nine rules of Extreme Programming that Don Wells published in 1999 and revisits each one for a team of people with agents on tight leashes. It's free, and nothing is for sale.

Why you're here

Stephen Margheim works with me at ZAR, and he put this link in the show notes for his episode of Matt Swanson's YAGNI. The show takes its name from Extreme Programming. So does IMP.

Where you'll recognize it

• Rule 16: Experiment on what to build. Boil the lake on how you build it. YAGNI still holds for scope. Once your experiments show you the feature, build it complete.
• Rule 26: Every test must prove it's worth keeping. Agents will write thousands of tests you don't need, and mutation testing decides which ones stay.
• Rule 17: Keep it regenerable. Regenerate when it's worth it. Stephen pushes back on this one in his essay on the site, "Code Is Cheap Now. That's Why It Matters."

Once you're in, start with the intro, "eXtreme Programming, Revisited," then read the rules side by side, 1999 next to 2026.

The ask

Tell me which rules you aren't gonna need. Pick one and write about it, for or against. If you've already written something, bring it along with a link back to the original, so the credit stays yours. It goes up under your name, and you approve the final text first.

Obie