Welcome, Berlin.rb

Impatient Programming takes the 29 rules of Extreme Programming that Don Wells published in 1999 and asks one question of each: what does that rule look like when typing is nearly free and you have a team of coding agents at your side?

The answer is not "the same, but faster." Some rules change completely. Spike solutions become cheap, so you run several in parallel and let the results argue it out. Stand up meetings become briefs written by your agents. Other rules turn out to matter more than ever, like keeping your agents on a tight leash and agreeing on the Contract before anyone writes code.

I practice this with my team at ZAR, and it is working well enough that I wrote it all down. The site is in preview and closed, so you need an email to get in. Once you are in, start here:

Where to start

• The intro, "eXtreme Programming, Revisited", where I make the argument
• The twenty-nine rules, 1999 next to 2026, side by side
• Born at ZAR, the case study where we deleted working components and regenerated them from the Contract
• The Tools page, open source tools that enforce the rules
• The values, if you want the why behind the rules

If a rule pushes back at you, good. Write an essay about it. Pick one rule, agree with it, extend it or push against it, and I will publish it once you approve the final text.

Obie