The Rogue
Rules are for people who get caught.
The Rogue operates outside the team's agreed processes. They paste code from the model directly into production, skip code review, and treat guardrails as suggestions. Speed is the argument, and the damage is someone else's problem.
- Symptom
- Hot-fixed branches, missing tests, and 'I'll add the review later' that never comes. Things ship. Other things break quietly.
- Why it matters
- Rogues create most of the silent quality collapse you cannot see in dashboards. Each shortcut is small. The compound interest is brutal.
- What the chapter gives you
- How to harden the guardrails without slowing the team, the policies that are worth enforcing, and how to redirect Rogue energy into work that doesn't blow up the codebase.
Anti-Patterns
- Bandit of Borrowed Brilliance
- Outlaw of AI Plunder
- Shadow Patcher of Ephemeral Solutions
Artifacts
- Cloak of RAG
- Dagger of Terms Violation
- Mask of Stolen Insights
From Volume 1 of The AI Developer's Field Guide
Read the full chapter in The AI Developer's Field Guide.
Get the book
Or choose your store:
Recognize this one in your codebase?
The book has the full chapter, the symptoms, and the interventions.