Developer field guide

Recognise the twelve ways AI coding quietly goes wrong before they ship.

When the AI Cuts Corners — Twelve AI Coding Failures and the Check That Catches Each

24 pages Screen-friendly A5, prints on A4 and US Letter Read on screen, or print Last reviewed July 2026 Version 2026-07

When you build with an AI assistant, the same handful of failures come up again and again: the test that quietly got deleted, the package that does not exist, the confident answer that is simply wrong. This 24-page field guide names the twelve most common ones — organised as pattern cards in four families — and gives each a sixty-second check and a fix, whether you are a beginner who cannot read the code yet or a professional reviewing an agent's pull requests.

Buy now · $11.24

Instant PDF download after checkout on Payhip. Nothing is shipped.

Cover of When the AI Cuts Corners — Previews show each page at reduced resolution; the download is the full print-quality PDF.

What's inside

Incentives, not malice — why capable tools produce these failures, in plain language
The test family: vanished tests, the weakened assertion, and the test edited to pass
The diff you did not order: invented packages, silent scope creep, and the 300-line function
Wrongness that smiles: the confident wrong answer, the happy-path-only build, and quiet data loss
The trust boundary: the security shortcut and the fabricated completion claim
A sixty-second check for every one of the twelve, with a worked specimen
Reading the signs early — the tell that appears before each failure bites
A one-page pre-ship checklist you can run in fifteen minutes, plus a plain-language glossary

Who it's for

Beginners who can't read the code yet but need to catch what the AI got wrong
Professionals reviewing an agent's pull requests

Who it's not for

Developers who don't build with AI assistance — every pattern here is about AI-generated code
Anyone wanting deep tool-specific tutorials — the book is pattern-first and tool-agnostic on purpose

The twelve patterns are drawn from published research on reward hacking and from the failures builders hit in real work; the checks can be run yourself, today, for free. Tool names and behaviours were last reviewed July 2026 — the patterns themselves have been stable for years and are the durable part. No named companies, no invented statistics, no customer stories.

Guidance, not gospel — this is a practical organisation tool, not legal, tax, medical, or religious authority.