Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

AI-generated code is embraced because its purpose is purely functional. In contrast, AI-generated content ('work slop') is met with skepticism because documents are often proxies for evaluating a person's thinking, competence, and trustworthiness, creating a social friction that AI tools must overcome.

Related Insights

A teammate of Charlie Marsh admitted they now review his pull requests more carefully, saying, 'you're not writing it anymore, it's the agent.' This highlights a hidden cost of AI adoption: it can break down the earned trust and review shortcuts that senior engineers typically benefit from.

Relying on AI without applying critical thinking produces "work slop"—outputs that look polished on the surface but lack genuine depth or substance. This can be dangerously misleading and devalues the quality of work by giving a false sense of security.

An Anthropic study on user behavior found that as AI generates more polished outputs like working code, users become less evaluative and more trusting. This "verification gap" is a critical flaw in human-AI collaboration, as polished results should trigger more scrutiny, not less.

The primary issue with low-effort AI-generated work is not its poor quality, but how it transfers the cognitive burden of correction and completion to the recipient. This 'masquerades' as finished work but creates interpersonal friction and hidden rework, fundamentally shifting the responsibility for the task's success.

Submitting generic, unedited AI-generated text or images is perceived negatively by sophisticated audiences. It signals a lack of effort (lazy), an unawareness of its generic appearance (stupid), or an attempt to mislead (evil). This highlights the new social codes emerging around AI usage.

Early AI adoption in software development saw a split: experienced engineers dismissed AI-generated code as low-quality 'slop', while junior developers, less able to discern its flaws, embraced it more readily. This highlighted a significant skill and trust gap.

Messy AI-generated code ("slop") can still result in a functional product, hiding imperfections from the end user. In knowledge work, a slightly "off" AI-generated contract or memo creates immediate legal or business risk, as there is no interface to abstract away the sloppiness.

Public skepticism towards AI is increasingly driven by the daily experience of consuming generic, AI-generated emails and documents. This "work slop" wastes time and devalues human communication, creating professional fatigue and resistance to the technology.

Research highlights "work slop": AI output that appears polished but lacks human context. This forces coworkers to spend significant time fixing it, effectively offloading cognitive labor and damaging perceptions of the sender's capability and trustworthiness.

As AI masters content generation, it will handle the "blank page" problem. The crucial human task will then shift from creation to evaluation: defining what 'good' looks like, identifying AI failure modes, and building better verification systems to ensure outputs are trustworthy and useful.