The Meat Proxy Engineering

I've noticed a new breed of engineers emerging in the industry lately. A friend recently coined the term "meat proxy" for them, and it feels incredibly accurate.

Picture this: a Staff Engineer sharing raw Claude artifacts with a casual "maybe," shifting the burden onto the rest of the team to verify what their AI actually generated.

What exactly makes someone a meat proxy? It usually comes down to three things:

1. Zero-Value Routing: They act as a simple conduit between an AI and the team chat or codebase. They don't process or filter the information; they just forward it.
2. By dropping a raw artifact with a "maybe this works," they outsource the actual engineering—verification, testing, and edge-case handling—to whichever unlucky teammate reviews their work.
3. They generate massive volumes of code or architecture documents incredibly fast, but the net productivity of the team actually drops because of the massive cognitive load pushed onto reviewers.

Let me know if you have seen a meat proxy