Essays
These essays come from people who've been at this a while, each one revisiting the rules they care about. Some extend a rule. Some push back on one, and when they do, IMP changes. That's rule 11: fix IMP when it breaks.
-
One person, a coordinator and a flock: running Impatient Programming alone
I ran Impatient Programming on three of my projects, with one person deciding, a coordinator agent I call a Shepherd, and delegate agents that build, check and review. Here is what helped, what it cost, and what I would change in the method.
extends rule 9 extends rule 11 agrees with rule 13 agrees with rule 19 agrees with rule 20 pushes back on rule 24 agrees with rule 26 pushes back on rule 27 agrees with rule 28
-
Keep pairing with humans
Rule 21 was never only about the code. Agents took over the navigator's job, and the second salary now buys focus, honesty, shared knowledge and someone who makes you stop for lunch.
-
Rule 17: What the Contract can't hold
The Contract keeps what the software must do. A regenerated component also needs to know which approaches the team already tried and ruled out.
-
Stop Apologizing for Being the Bottleneck
Some constraints are blockages. Others are the most deliberately engineered part of the system.
-
Code Is Cheap Now. That's Why It Matters.
Code is fungible now, and that's exactly why its quality compounds. Every coding agent reads the codebase before it writes a line.