Tuesday Aug 4
CULTUREOther

'Don't Be A Meat Proxy' Goes Viral

4AUG
MEAT PROXY

Engineering culture just got a name for its worst AI habit. A viral essay defines the meat proxy: someone who pipes agent output to colleagues without reading it. Simon Willison, veteran developer-blogger, co-signed the warning.

The pattern: a colleague submits Claude-generated code for review, reviewers leave feedback, and the author pastes that feedback back into the AI without ever engaging.

Willison says most of his code is now agent-written. The difference is he reads it and refuses to forward low-quality output to humans. Authorship is not typing. It is accountability.

The essay topped Hacker News the same week Greg Brockman flagged the Slack version of the problem. The industry is drawing etiquette lines around agents.

full brief & sources

⚡ Why this matters

  • Teams adopting AI coding tools need social norms, not just tooling - this essay hands them the vocabulary.
  • Review culture is where AI-generated work meets human accountability, and it is quietly breaking.
  • Naming an anti-pattern is how industries police it - meat proxy will show up in code reviews within weeks.

🔍 What happened

  • Aug 3 - the essay Don't Be a Meat Proxy went viral on Hacker News and Lobsters.
  • It describes engineers who relay AI output and reviewer feedback without engaging with either.
  • Simon Willison joined the discussion, distinguishing agent-written code from unaccountable code.
  • Willison: most of his shipped code is agent-written, but he reads everything before humans see it.
  • The term spread across tech forums within a day of publication.

💬 Smart takes

  • Simon Willison, developer-blogger: being a meat proxy is not the same as working with agents - the line is whether you engage with the output before forwarding it.
  • The essay's core charge: a meat proxy wastes reviewer time on work no human has actually read.
  • Skeptic: viral vocabulary fades fast - without tooling that surfaces who actually reviewed AI output, the norm has no enforcement mechanism.

🧭 Where this goes

  1. Likelyengineering teams write meat-proxy language into code review guidelines this quarter.
  2. Likelythe term escapes engineering into general knowledge work - AI-relayed emails, docs, and analyses.
  3. Possiblecode review tools add provenance signals showing whether the author engaged with AI-generated changes.
  4. Wild Carda company publicly ties promotion or performance review criteria to authorship accountability for AI output.

🥄 The Spoon Take

The interesting fight of this AI phase is not humans versus machines - it is humans deciding what they still owe each other when machines do the work. Meat proxy names the failure: passing along output you never read. Accountability, not authorship, is becoming the scarce resource.

🤔 Pushback

Every viral engineering essay feels like a turning point for a week - the incentive to ship fast with agents may simply outrun the shame.

·Simon Willison - Meat proxy note·Lobsters - Essay discussion·The World Times - Meat proxy history