You Are Not a Developer. You Are Wiring.

A blog post with a blunt title climbed to the top of Hacker News recently: “Don’t be a meat proxy.” It pulled 1,614 points. That number matters less than what it signals. The phrase is crude, and it stuck, because a lot of developers read it and felt caught.

What a Meat Proxy Actually Is

A proxy, in networking terms, is a server that sits between two systems and relays requests and responses. Stick “meat” in front of it and the relay is a person. You are the wiring.

Picture the loop. You ask the AI for code. You copy it. You paste it into the terminal. It errors. You copy the error. You paste it back into the chat. New code comes out. You copy that.

What is the human contributing here? Clipboard transport. No judgment, no comprehension, certainly no design. Just a biological cable running between two systems that would rather talk to each other directly.

Why This Landed in 2026 and Not 2023

Three years ago, AI coding tools were glorified autocomplete. The human drove; the model suggested. That relationship has inverted. Agents now read files, edit them, run the test suite, and report back. The human’s contribution has narrowed to pressing approve.

And that approval degrades fast. A hundred lines of generated code shows up in the diff. Do you read all of it? The first time, yes. By the tenth time, you skim. By the twentieth, you hit enter.

Here is the trap. The better the AI performs, the less carefully you read. The less carefully you read, the more you miss. And whatever you miss is still yours — the commit has your name on it, not the model’s.

The Real Risk Is a Comprehension Gap, Not Skill Decay

“Using AI will rot your skills” is an old argument. People said it about calculators. They said it about Stack Overflow. That version of the complaint is not interesting.

This post aimed somewhere more specific. The problem is not eroded skill. It is a comprehension gap — code in your repository that nobody on your team ever understood.

Copying from Stack Overflow at least required reading the answer. You saw the comments. You saw the guy pointing out that the accepted solution breaks on Postgres 14. You absorbed, roughly, the conditions under which the snippet worked. That friction is gone now. The code goes straight into the file.

The bill arrives during an incident. It is your system, and you cannot explain it. So you go back and ask the AI, at 2 a.m., what your own service does. And if it hallucinates an answer, you have no way to tell — you never built the mental model that would let you catch it.

The Fix Is Positional

The prescription is simpler than you would expect: stop standing between the systems and start standing above them.

Set a hard stop at three round trips. If the copy-paste loop has cycled three times without resolution, the problem definition is probably wrong. More prompting will not fix a misframed problem. Close the chat and go re-read the actual requirement.

Hand the wiring to a machine. Copying an error message from a terminal into a chat window is exactly the kind of thing a script does well. If you find yourself acting as a clipboard, that is a tooling gap, not a job description. Pipe the output. Use an agent that reads the terminal itself.

And hold yourself to one test: can you explain why the code is shaped the way it is? Not line by line. Nobody memorizes generated code. But the structure and the intent — where the boundaries are, what the tradeoff was, why this approach over the obvious one. If you cannot articulate that, what you performed was not review. It was a signature.

The Comments Did Not All Agree

Plenty of pushback showed up in the thread. The most common: fine, but what do you want me to do about it? The deadline is Thursday. The feature has to ship. There is no budget line for comprehension. That objection is hard to argue with, and the people making it were not being lazy.

A darker counterpoint came from the other direction. The proxy role is itself temporary. Tools are already closing the loop — agents that read their own terminal output, run their own tests, iterate without a human in the middle. If your entire contribution is clipboard duty, you are not being warned about becoming obsolete. You are being told the timer already started.

A third camp made the distinction that probably matters most: copy-paste is not the sin. Copy-paste as the default mode is. A shortcut you take under deadline pressure and a road you drive every day are different things, even when they follow the same path.

Look at Your Own Day

“Meat proxy” stung because it was accurate. Think about the last eight hours of work. How much of it was deciding something? How much was moving text between two windows?

As models take over the typing, the developer’s job shifts from hands to head — from the seat where code gets written to the seat where direction gets set. That seat is still open. But it does not stay yours by default, and if you leave it empty, the only work left in the room is wiring.