For teams

Why this works on a team

Most engineering anti-patterns get named in conversation, not in books. The trouble is that the conversations only happen after something breaks — and by then, the patterns have hardened into culture. The AI Developer's Field Guide gives a team the names before the breakage, so the next conversation can start at the pattern instead of at the person.

Use it in code review

Pair the book's review prompts with your existing PR template. Reviewers stop relitigating preferences and start asking the questions that actually catch AI-generated slop: where the model produced something polite and plausible, where the seams between generated pieces don't fit, where the test "works" but doesn't test anything load-bearing.

Use it in retros

Drop a monster name into the retro and watch the conversation get specific in under a minute. "I think we got eaten by the Scope Creep Kraken on Tuesday" is a much faster way into the real discussion than "I'm worried about how we're using AI." The metaphor is the on-ramp, not the destination.

Use it in planning

The Fighter, the Wizard, the Rogue, and the Cleric show up in planning long before they show up in incident reports. The book includes the questions that pull each archetype back toward judgment without slowing the team down.

Use it in onboarding

New hires inherit the team's habits within weeks. Hand them the field guide on day one, and they inherit a vocabulary too — one that lets them name what they're seeing without having to invent the language themselves.

Bulk orders

Buying for an engineering org? Bulk paperback orders are available through Amazon and Barnes & Noble. For larger orders (10+ copies) or invoiced purchases, get in touch and I'll point you to the right channel.

Contact about bulk orders