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
Artifacts
Want the full chapter? Grab the free cheat sheet, read an excerpt, or get the book.
Recognize this one in your codebase?
Free cheat sheet, excerpts, and interactive diagnostics.