Re:Being a meat proxy for AI should be grounds for getting p...
by Aozora7 on Monday November 09, 2026 @05:14AM
(#50423592)
The linked post describes being a meat proxy as copypasting tickets into AI and pushing the output without reading.
I don't copypaste tickets to AI, I decide on how each task is solved and LLMs only implement what I decided on. I read the code before making a PR. I review other's PR with my own eyes. I never copypaste LLM output to my coworkers in chat. What else is there to it?
Re:Being a meat proxy for AI should be grounds for getting p...
by _nalply on Monday November 09, 2026 @05:51AM
(#50423869)
It's fine. What I do my hobby programming, I switched to Pi as harness, and instructed the model to careful stop early such that I can stare at code, and I tend to give extremly substantive feedback sometimes. It was not easy, and now I hope I found something that clicked for me. I modified the bash tool to force the agent to tell me what he does, and it helps wonders, the agent says, he wants to do X and I can verify if the bash commands do what the agent says. I also use lightweight sandboxing.
Okay, now that that is out, let me ask politely: in what way do you avoid acting as a meat proxy for AI?