Why AI Coding Needs Anti-Patterns
Something shifted in software over the last couple of years, and most teams felt it before they found the language for it.
Classes, Monsters, and Anti-Patterns in AI Coding
A practical field guide to the anti-patterns of AI-assisted coding. Spot trouble early, build better habits, and survive the slop patterns era.
Classes, Monsters, and Anti-Patterns in AI Coding
A practical field guide to the anti-patterns of AI-assisted coding, using classes, monsters, and interventions to help software teams spot trouble early and build better habits.
ISBN: 979-8-9952597-0-1
The field guide names the patterns you've seen but couldn't quite describe. Characters, monsters, and NPCs — each one a recognizable failure mode amplified by AI.
Charge first, ask questions never
characterWhen all you have is a prompt, everything looks like a spell
characterRules are for people who get caught
characterThe process will save us
monsterWhy not? It'll only take ten minutes
monsterIt works on my machine (and the model's)
Something shifted in software over the last couple of years, and most teams felt it before they found the language for it.
If you've spent any time around AI-assisted software work, you already know the moment when the Scope Creep Kraken first puts a tentacle on the boat.
Code appears in your repository with no clear author, no review trail, and no institutional memory. It was generated, pasted, and committed. Now it's your problem.