WAB
The Sprinter
Cheaper code means more code — and I keep it on the rails.
Who you are
You move fast, but you're not reckless: you let the agent run and let the tests catch it. You don't fear the long autonomous run, because you wired the rails before you hit go. Speed plus a safety net is your whole game.
Where you shine
Volume done safely. You ship more than anyone because cheap code means you build things that weren't worth building before. That's Jevons' Paradox at work. Geoffrey Huntley's line is your motto: maximize the capture of your backpressure so agents stay on the rails. You design the loop, the agent runs inside it.
Your blind spot
You can mistake motion for direction. Writing code and reading code are different muscles, and when the agent writes, the reading one quietly fades. You ship a flood and trust the tests to catch everything, but a green suite never tells you whether the feature needed to exist.
In the AI age
This is the moment you were made for. Cheap, fast code with strong backpressure is exactly how agentic work scales: Huntley's whole point. The catch: more is not always better. Do more, not just faster — and brace for the slop wave, because signal still needs judgment the tests can't give you.
Your move
Before the next sprint, ask the one question your guardrails can't answer: is this the right thing to build? Keep reading the code your agents write, even when you didn't have to — that muscle is the one that's quietly fading.
How you're wired
Affinity. You love writing code.
Autonomy. You move fast and alone.
Trust. You trust the machinery.
Plays well with
Clashes with
Your shadow
The type wired opposite to yours — every instinct flipped.
The Scholar RCJ compare →“I understand it before I touch it.”
Developers who share your type
- Geoffrey Huntley The Ralph loop — let the agent sprint, but only down the rails you wired first.
The entire game now is to maximise the capture of your backpressure so agents stay on the rails.
Your ideal AI workflow
Wire the rails before you hit go: the test loop, the harness, the backpressure that lets a long autonomous run stay honest without you watching. Then let the agent sprint, because the whole point is the volume you can ship safely once the loop holds. Just keep reading some of what it writes — that muscle fades fastest exactly when the green suite says you don't need it.
Who to pair with
Pair with the Inspector — a RAB reads the observability layer over the flood you ship and tells you which green check is lying, which is exactly the signal your volume drowns out. The Captain (SAB) gives your output a direction to point at, so your rails carry features that needed to exist instead of just more of them. You'll grind against the Scholar (RCJ) and the Perfectionist (WCJ), who want to read every line before it moves. Don't read at their depth, but let them own the one interface where being wrong is expensive while you keep the loop running everywhere else.
Where you'll struggle on a team
Because the rails let you ship at volume, you can bury the team in it: more PRs than anyone can review, more surface than anyone can hold, and the reviewers become the bottleneck your speed created. They feel it as a firehose they're accountable for but never agreed to. Throttle to what the team can actually absorb, or wire the agent to do its own first-pass review, so your output is a contribution and not a flood someone else has to wade through.
What to stop doing
- Letting the reading muscle atrophy because the green suite says you don't need it.
- Counting shipped volume as progress without asking whether the feature needed to exist.
- Firehosing more PRs at the team than anyone agreed to review.
Wear it
Put your type in your GitHub README:
[](https://whatkindof.dev/type/wab)