Anti-patterns: things to avoid

· Source: Simon Willison's Weblog · Field: Technology & Digital — Software Development & Engineering, Artificial Intelligence & Machine Learning, Emerging Technologies & Innovation · Depth: Intermediate, quick

Summary

This content identifies a critical anti-pattern in "agentic engineering": submitting unreviewed, agent-generated code to collaborators via pull requests. The author emphasizes that developers are responsible for ensuring agent-produced code is functional and ready for review, rather than delegating this initial validation to others. A good agentic engineering pull request should feature working, small, well-contextualized code, with human-reviewed descriptions. To demonstrate due diligence, developers are advised to include evidence of their self-review, such as testing notes or screenshots, ensuring reviewers' time is respected. This discussion is a chapter from the comprehensive guide, "Agentic Engineering Patterns."

Key takeaway

A critical anti-pattern in agentic engineering is submitting unreviewed, agent-generated code in pull requests, effectively delegating your initial validation work to collaborators. To mitigate this, developers must self-review agent-produced code, ensuring it's functional, small, well-contextualized, and accompanied by validated descriptions and evidence of manual testing or specific implementation choices. This discipline significantly improves team collaboration, code quality, and overall efficiency in agent-assisted development workflows.

Topics

Best for: Software Engineer, AI Engineer, Machine Learning Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Simon Willison's Weblog.