Values

Lazy, impatient and proud

The name of our methodology comes from Larry Wall, one of Obie's earliest programming heroes. In the seminal O'Reilly book Programming Perl he listed the three great virtues of a programmer: laziness, impatience and hubris. All three of those virtues are safer than ever to practice in earnest when we're using AI coding agents to do our typing for us, as long as we put guardrails in place to keep the clankers disciplined.

XP values shaken up with Larry's three virtues make a delicious cocktail.

Impatience, kept honest by feedback

Huff rides a skateboard at full speed holding up a stopwatch, towed on the leash by his little orange robot sprinting ahead.

This one is in the name. We're impatient. We want to ship as much as possible, as quickly as possible, so speed is a core value. We read as little code as possible. We have zero tolerance for technical debt, it gets eliminated immediately. Every merge gets released. The customer sees the work this week. A known-wrong shape doesn't get to live another day.

In the rules: Every green merge is a release, ideally, No timeboxes. A weekly showcase is the heartbeat, Spikes are cheap, so run several in parallel.

Essays Sebastian Scholl, “Stop Apologizing for Being the Bottleneck” pushes back

Revisit this value

Laziness, kept honest by simplicity

Huff lounges in a striped deckchair under a beach umbrella in sunglasses, sipping a drink, while his little orange robot types on a laptop beside a row of finished sandcastles.

Wall's lazy programmer goes to great lengths to save effort overall. In IMP that means putting an enormous amount of effort into continuous (and ideally automated!) guardrail engineering, so that no coding agent ever makes the same mistake more than once. It also means doubling down on convention over configuration and expressive language. In the most extreme implementations of IMP, we completely hand over ownership of maintenance work to autonomous agents.

In the rules: Guardrails fire on every change, Move attention around, Standards are enforced by machines.

Revisit this value

Hubris, kept honest by respect

Huff stands on a gold first-place podium holding a trophy aloft while his little orange robot polishes the podium until it sparkles.

Wall's proud programmer writes code that other people won't want to say bad things about. We might engage in goldplating, but the result is still going to be code that is as close to architectural perfection as possible. With great AI powers comes a great need for respect, to avoid tossing slop grenades to our teammates. There's no excuse for low standards anymore.

In the rules: Experiment on what to build. Boil the lake on how you build it, Simplicity: breathe in, breathe out.

Revisit this value

XP's values carry over

Huff sits cross-legged reading a white copy of Extreme Programming Explained, his little orange robot leaning in to look.

XP's own values carry over untouched: communication, simplicity, feedback, courage and respect. Imps are well-versed in classic software engineering best practices and don't dismiss rigor just because AI is magical.

Revisit this value

Heart

Huff high-fives a grinning human programmer in a hoodie while his little orange robot holds up a red heart balloon.

But our biggest value of all is heart.

Jerry Weinberg said that no matter how it looks at first, it's always a people problem. We believe the reverse is true too. Anytime a software project wins big, it's always because the humans involved are amazing. Putting people first is the most impish thing you can do in the age of clankers. Putting the needs of humans first is what makes IMP a part of the Agile tradition.

Larry Wall named the virtues. Gerald Weinberg taught us it's always a people problem: it's his Second Law of Consulting.

Revisit this value