@mattpocockuk: Don't blame the agent for writing the bad test Blame the codebase for allowing the bad test to be written
Summary
Matt Pocock argues that when AI coding agents write bad tests, the fault lies with the codebase structure that permits such tests, not the agent itself.
View Cached Full Text
Cached at: 10/12/26, 11:25 AM
Don’t blame the agent for writing the bad test
Blame the codebase for allowing the bad test to be written
Similar Articles
@mattpocockuk: In a phrase, "make bad code unrepresentable"
Matt Pocock argues that in the AI coding era, developers should embrace more abstractions combined with strict lint rules to constrain AI agents to making only good design decisions.
@mattpocockuk: "No tautological tests"
A tweet criticizes the AI model Opus for adding excessive unit tests for simple constant strings, highlighting issues with tautological testing in AI-assisted development.
@mattpocockuk: Some mistakes you might be making: Your effort level is too high Your skills are too long You're not aligning before yo…
Matt Pocock lists common mistakes developers make when working with AI coding agents, including misaligned effort, overly long prompts, weak automated checks, poor codebase navigation, and insufficient agent autonomy.
Nobody's Testing AI Coding Agents Enough
This article discusses the insufficient testing of AI coding agents, highlighting a critical gap in ensuring their reliability and safety in software development.
@mattpocockuk: If your code sucks, your agent will too. So, software fundamentals matter more than ever. That's why I'm interviewing @…
Matt Pocock announces a live interview with Uncle Bob about software fundamentals and their importance for AI agents, scheduled for Wednesday on YouTube.