News for hackers. Stuff that matters.
Re:Being a meat proxy for AI should be grounds for getting p... by jongjong on Monday November 09, 2026 @02:44AM (#50422374)
Morally speaking, the AI was trained on our code. It's our right to be meat proxies, so long as we deliver.

Also, practically speaking, if the codebase is well designed and has good foundations, being a meat proxy might actually work. If someone puts careful, meticulous thought into getting the foundations of the project right and then turns into a meat proxy because the thing practically builds itself, should they be fired?

If this is the case, then developers have the incentive to create a rotten overengineered foundation, then the AI won't be able to get anything done without human guidance.

What the author is suggesting isn't only immoral, it's retarded. It's why we're in the mess we are in now with projects with millions of lines of code with new critical vulnerabilities popping up daily. Show me the incentive, I show you the outcome.

Re:Being a meat proxy for AI should be grounds for getting p... by justinpw on Monday November 09, 2026 @10:07AM (#50426685)
You capture a bit of the nuance that drew me here to comment.

There is a maxim somewhere in here, but I'm not going to keep trying to get it just right, instead, here are some more specific elements of it:

- I might want to put little effort into my work, and poorly execute on AI offerings to amplify my output.

- I might want to put little effort into my work, and put together a nice prompt/context/harness to amplify my output.

- Ambitious laziness is the driver of countless effective products and services.

There is a broad spectrum of AI uses and practices, and we need to keep hammering away at figuring out how to make technology serve all people.