News for hackers. Stuff that matters.
Re:Being a meat proxy for AI should be grounds for getting p... by dawnerd on Monday November 09, 2026 @02:27AM (#50422225)
It’s wild to me how many software engs never want to see code again. IMO they should just retire so someone else that does want to look at code can take the job. The laziness is unreal, all while the same people acting like they’re productive.
Re:Being a meat proxy for AI should be grounds for getting p... by eshack94 on Monday November 09, 2026 @02:29AM (#50422242)
Cannot agree more.
Re:Being a meat proxy for AI should be grounds for getting p... by apples_oranges on Monday November 09, 2026 @02:33AM (#50422276)
Nature is lazy. And as long as they take responsibility for their merge requests (and understand them) ..
Re:Being a meat proxy for AI should be grounds for getting p... by B4uler5 on Monday November 09, 2026 @04:52AM (#50423395)
This is my problem with it, I can’t tell if people actually think the LLMs writing all their code is the future or they just want it to be the future because they’d prefer not to think and still get a dopamine hit from it.
Re:Being a meat proxy for AI should be grounds for getting p... by g-b-r on Monday November 09, 2026 @04:54AM (#50423417)
And how would they understand them if they didn't even read them?
Re:Being a meat proxy for AI should be grounds for getting p... by exitb on Monday November 09, 2026 @02:33AM (#50422278)
To a very large degree, it's the employers who push toward that direction. When you talk about traditional engineers replacing vibe coders, is there actually a market for it?
Re:Being a meat proxy for AI should be grounds for getting p... by pona-a on Monday November 09, 2026 @02:34AM (#50422288)
[delayed]
Re:Being a meat proxy for AI should be grounds for getting p... by Aozora7 on Monday November 09, 2026 @02:39AM (#50422340)
I got into this field because it's the highest paid job I have aptitude for, not because I was ever particularly excited to write jobslop code that consists mostly of basic CRUD and business logic.

I don't act as a meat proxy since I have some respect for myself and my coworkers. However, whatever interest in programming I ever had, was completely gone after a couple of years on the job.

That being said, I am, in fact, speedrunning early retirement.

Re:Being a meat proxy for AI should be grounds for getting p... by _nalply on Monday November 09, 2026 @03:21AM (#50422651)
Thanks for your honesty. It explained some things I watched before retiring. I am one of those people who loved programming and hated what corporate settings made out of it. Yeah, it's one of the better paid things. It's hard work, and there are things that pull it in exactly opposite directions. Sometimes even for simple things like CRUD, when something is requested that would go sideways, you have the choice of rejecting it and avoiding thinking hard, or taking it by the horns. I told my wife, sometimes you just can't leave, and it's not only emergencies. Because if you are in a deep session and you stop, you lose your own context. But it's very satisfying if you can wrap it up in a way that leaving notes for yourself for later suffices. But this style of work is not for everyone. And in corporate settings weird things happen, and sometimes I just felt shat on. But hell, it's paid well, right?

Okay, now that that is out, let me ask politely: in what way do you avoid acting as a meat proxy for AI?

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.
Re:Being a meat proxy for AI should be grounds for getting p... by noosphr on Monday November 09, 2026 @02:51AM (#50422425)
,s/code/machine &/g

Your job was never code.

Re:Being a meat proxy for AI should be grounds for getting p... by acron0 on Monday November 09, 2026 @03:23AM (#50422667)
Do you think you're better than them? Is it possible they understand something you don't? What does "software engineer" even mean?
Re:Being a meat proxy for AI should be grounds for getting p... by Nursie on Monday November 09, 2026 @03:51AM (#50422902)
What if I, as someone employing you, don't specifically need someone to look at the code?

We may not be quite there yet, but what if automations using LLMs can do it faster than software engineers who look at the code can, and to an acceptable standard?

> all while the same people acting like they’re productive.

Are they delivering features, capabilities, updates, refactors etc? Faster than those who are "looking at the code" ?

Don't get me wrong, I've spent 25 years reading and writing code, I'm pretty sure I'm quite good at it, though I wouldn't claim to be any sort of superstar. My job has changed immeasurably in the last year, and I'm starting to wonder if "reading the code" won't go the same way as "verifying the assembly that the C compiler spits out to make sure it's correct"

Re:Being a meat proxy for AI should be grounds for getting p... by B4uler5 on Monday November 09, 2026 @04:47AM (#50423349)
A compiler is deterministic, even if you don’t understand the assembly at least it will do exactly the same thing every time. I absolutely loath this comparison.
Re:Being a meat proxy for AI should be grounds for getting p... by theshrike79 on Monday November 09, 2026 @07:17AM (#50424571)
[delayed]
Re:Being a meat proxy for AI should be grounds for getting p... by Eddy_Viscosity2 on Monday November 09, 2026 @07:44AM (#50424814)
Carpenters can and do make more money when they make things by hand. But the customers base for this is indeed smaller.

It's like complaining about a chef who make all their food from fresh ingredients instead of buying off-the-shelf processed versions. People will pay more for that freshy made food.

Re:Being a meat proxy for AI should be grounds for getting p... by 28304283409234 on Monday November 09, 2026 @09:47AM (#50426382)
But to call one or the other 'lazy'? It is just different.
Re:Being a meat proxy for AI should be grounds for getting p... by Eddy_Viscosity2 on Monday November 09, 2026 @11:32AM (#50427860)
Sometimes its different and sometimes it is just being lazy.
Re:Being a meat proxy for AI should be grounds for getting p... by theshrike79 on Tuesday November 10, 2026 @05:22AM (#50438288)
[delayed]
Re:Being a meat proxy for AI should be grounds for getting p... by laserDinosaur on Monday November 09, 2026 @12:50PM (#50428894)
> I get paid to solve problems, not to write code. Before writing code was required to solve the problem, it's not a hard rule anymore.

I think that's the difference though. I commented on a similar topic earlier, but I think the issue is that people are using these tools for both the coding AND the problem solving. They've turned over both ends of the workflow to the bots. When you ask them "Why did you add these new libraries to our project to solve this?" you get "I dunno, Claude did it". When you ask "Why did you avoid using our entire DI system for these static vars?" they respond "I dunno, Claude did it. But the tests pass!".

If you still tackle the problem solving part, that's great. Thank goodness. But I wouldn't assume that's how the rest of the lazy gits are using LLMs as well.