Graphite pencil illustration of the Fighter archetype, a developer charging forward with a language model

The Fighter is defined by a bias toward action so strong that it can crowd out reflection. They trust their tools, their instincts, and their ability to power through consequences. AI tools amplify almost every one of the Fighter's instincts — and that's the problem.

Symptom
Two hundred lines of plausible code in thirty seconds, merged before lunch. Velocity metrics love them. Postmortems hate them.
Why it matters
Fighters do not produce slop because they are careless. They produce slop because they are fast and confident, and AI makes them faster and more confident — even when that confidence is no longer earned.
What the chapter gives you
How to spot Fighter behavior in PRs, the conversation to have without making it personal, and the team rituals that protect a Fighter from their own velocity.

Anti-Patterns

Artifacts

  • Debugging Greatsword
  • Design Patterns Relic
  • Unapproved Gauntlet of Power

From Volume 1 of The AI Developer's Field Guide

Read the full chapter in The AI Developer's Field Guide.

Recognize this one in your codebase?

The book has the full chapter, the symptoms, and the interventions.