Generation Is Cheap, Review Is Expensive: How to Stop Shipping AI Slop — Gabriel Martinez, G2i
Gabriel Martinez argues that the current AI-driven development cycle is prone to 'slop'—work that appears finished but lacks deep human judgment, ownership, or understanding. He asserts that while generation is cheap, evaluation and maintaining system coherence are expensive. The core message is that engineers must slow down, prioritize clear conventions, and shift the review surface from massive code blocks to high-level diagrams and defined boundaries to prevent the codebase from becoming an unmanageable 'ball of mud.'
Key takeaways
-
Defining Slop
0:37
Slop is not AI-generated code, but rather work product where ambiguity was cleared with guesses, trade-offs were left to chance, and ownership was not taken. The danger is that the engineer never noticed the choice or constraint that needed to be addressed. (0:37)
-
Code as a Liability
5:06
The cost of understanding a software program is not falling, even as the cost of writing code decreases. Good software must reflect the shape of the domain, and AI cannot magically give a messy system coherence. (3:06)
-
The Review Bottleneck
16:54
External pressures and the speed of AI generation lead to massive PRs and bloated documentation, shifting the cognitive burden to the reviewer. Generation is cheap, but evaluation is expensive. (8:45, 10:14)
-
Optimizing for Human Judgment
To combat slop, teams must adopt conventions, use diagrams as the primary review surface (showing service boundaries, data flows, and state transitions), and establish clear ownership boundaries. (12:34, 14:13)
-
The Role of ORC
The speaker's company, G2i, built ORC to address the failure pattern: AI can generate code, but the surrounding discipline (planning, review, context management) is still required. ORC aims to preserve human responsibility while leveraging AI's generation capabilities. (15:43)