A while back, I noticed that using Claude all day left me feeling mentally tired. After thinking it over, I realised the problem was Claude’s complex language. I’ve used English daily for years, so that shouldn’t be an issue. To compare, I switched Claude to my native language and had the same problem the author described. The text still needed to be literally deciphered before I could understand it. After talking wi…
Don't be a meat proxy
721–730 of 787 posts
Re: Don't be a meat proxy
#722Earlier quoted context omitted.
Same. I'm being forced into a position where I'm supposed to do everything with AI agents, not write any manual code, and only act as a reviewer. It sounds like you know the drill. It may push me into early retirement.
The last straw (of many last straws) was over the weekend a co-worker sent me a chat "hey can you click approve on this PR real quick?". This only makes me click "Apply" (jobs) instead of "Approve".
Re: Don't be a meat proxy
#723Earlier quoted context omitted.
I had an encounter with the opposite problem the other day, PM asked me if the library I was using for randomization was "secure" and I said, "Yes, I used the standard Java library for cryptographically secure random numbers that is already used in several other locations in this project," and he said, "But did you ask Claude if it's secure? It has to be secure!"
Asking someone to ask an LLM is peak laziness.
Managers tell the developers to talk to LLMs.
CEOs tell the managers to tell the developers to talk to LLMs.
The longer the chain, the higher you are in the company hierarchy.
Re: Don't be a meat proxy
#724Earlier quoted context omitted.
At my dayjob there is a person spearheading ai across the enterprise. They generated lots of documentation across the whole stack and now makes all PO/BAs read it if it's correct. So not just 300 lines - he unironically generated thousands of lines of "documentation" and is now making hundreds of people review it for him Complete brainrot Au psychosis is getting seriously outrageous at this point Thankfully I'm a dev…
When some people call this "Verification Debt" or something similar, that is setting the Overton Window upon this phenomena adversely upon the verifiers. I call it an application of Brandolini's Law: "The amount of energy needed to refute bullshit is an order of magnitude bigger than that needed to produce it."" Until you put in at least the same amount of energy required to verify the AI output as you are asking oth…
Re: Don't be a meat proxy
#725I deal with this all day long at work and it’s exhausting. People almost acting like no one has thought of it “I asked Claude what happened, and it spit out this 300 line response. Can you read it for me and see if it’s right?” What kills me is you might expect this from a busy high level manager that doesn’t really understand the technical details and they just point the AI to an error they got. They don’t know how…
I had an encounter with the opposite problem the other day, PM asked me if the library I was using for randomization was "secure" and I said, "Yes, I used the standard Java library for cryptographically secure random numbers that is already used in several other locations in this project," and he said, "But did you ask Claude if it's secure? It has to be secure!"
Repeat for all instances of micromanagement until they learn to trust your judgement and expertise.
Re: Don't be a meat proxy
#726Why aren't we seeing these type of articles talking about the first bottleneck? Even the ones talking about code review don't mention the upstream work.
Writing software is still one of the most expensive things you can do to a business even with LLms.
Re: Don't be a meat proxy
#727Earlier quoted context omitted.
I just can’t understand why this is not a fireable offense. Like, I can see getting a strong warning the first time somebody notices you do this, then if you persist you’d have to be let go. Just like anybody else who is clearly not doing their job. Why would you tolerate this sort of behavior at your company?
I get it’s annoying and I personally hate it but firing someone for it is ridiculous. Are you expecting everyone to rewrite everything from an AI before they share it because that doesn’t sound a good use of company time either.
Why NOT fire them?
Re: Don't be a meat proxy
#728Earlier quoted context omitted.
I know exactly the persona you’re describing. It’s unfortunate because they have a great learning tool now. I always felt bad for over eager engineers who were not strong. They had the right attitude but I thought lacked the learning resources and perhaps the learning skills others stronger engineers had. Before if you found yourself in an area you don’t understand. Some people make it all the way through school with…
So, in other words, the pipeline that's producing engineers is not filtering out people without talent. It used to be that people who "didn't know how to learn" couldn't make it through the early engineering courses and moved over to some other field.
HR likes tech bros who know how to play the game. They hate nerds who point out risks.
This all started with the cryptocurrency gold rush.
Re: Don't be a meat proxy
#729Earlier quoted context omitted.
I just can’t understand why this is not a fireable offense. Like, I can see getting a strong warning the first time somebody notices you do this, then if you persist you’d have to be let go. Just like anybody else who is clearly not doing their job. Why would you tolerate this sort of behavior at your company?
Because it's harder to fire managers. And even harder to fire executives. Who goes when companies need to downsize? Rarely executives; they'll always find a way to be retained...hell, they're the ones with the power to decide who goes.
Re: Don't be a meat proxy
#730Earlier quoted context omitted.
Some skills are easy re-pick-uppable, like bicycling. Mathematics is probably more challenging. Not sure about programming, especially "borint" business-like programming.
Nah. After you have those skills, they don’t go away. Math: the most important stuff is the biggest picture. If you learned it properly (not just memorizing), that’s the last to fade. With programming, the details change but the fundamental skill doesn’t. Or hadn’t as of a few years ago.