@mattpocockuk: Some mistakes you might be making: Your effort level is too high Your skills are too long You're not aligning before yo…
Summary
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.
View Cached Full Text
Cached at: 10/13/26, 01:45 PM
Some mistakes you might be making:
Your effort level is too high Your skills are too long You’re not aligning before you start work You’re aligning too often, and too hard Your automated checks are too lax Your custom tooling is too token-inefficient You aren’t doing enough automated review You aren’t reviewing previous coding sessions (with an agent) You’re doing too much human review You aren’t vibe coding enough prototypes Your agent can’t verify its own work You’re babysitting the agent too much You’ve overloaded your global steering files Your codebase is hard to navigate You aren’t building a shared language Your codebase architecture allows bad tests to be written You aren’t thinking strategically enough You aren’t thinking enough
Similar Articles
after a year of shipping with AI agents, here's what they still reliably get wrong
A developer shares consistent failure modes of AI agents after a year of shipping code with them, including confidently wrong code, inability to maintain cross-file architecture, lacking pushback on bad decisions, and security edge case issues.
@mattpocockuk: Do you feel in control when you're coding with AI? Can you: - Get it to build the thing you wanted? - Stop it making th…
A promotional tweet for a new course aimed at helping developers achieve better control and efficiency when coding with AI, addressing issues like accuracy and task management.
@PawelHuryn: 7 truths about working with coding agents, learned the hard way: 1. /goal is not enough. Explain the why + strategic co…
An experienced developer shares 7 key insights on effectively working with AI coding agents, emphasizing the need for strategic context, documentation, and human oversight for better outcomes.
@mattpocockuk: Don't blame the agent for writing the bad test Blame the codebase for allowing the bad test to be written
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.
Is anyone else noticing that people building AI agents are forgetting basic software engineering?
A practitioner argues that AI agent builders are rediscovering problems that basic software engineering—input validation, data modeling, process isolation, access control—already solved, and that vibe coding skips these cross-cutting concerns. The post calls for applying established design and architecture principles to agent workflows.