Live data from Hacker News

Don't be a meat proxy

gruhn.me

731–740 of 787 posts

Re: Don't be a meat proxy

#731

Earlier quoted context omitted.

I think people tend to forget that not only do we ourselves have different skillsets and can be amazing at one thing but horrible but another, but this also applies to other people in the world! Far all we know, there is an amazing developer out there who without LLMs, might have been the single best developer in the country, but even this person might not be able to figure out how to effectively work with LLMs. And…

> Far all we know, there is an amazing developer out there who without LLMs, might have been the single best developer in the country, but even this person might not be able to figure out how to effectively work with LLMs. And vice-versa too. If working with LLMs effectively means accepting subpar results or be a reverse centaur, then I’d be glad not to be able to work with them. I’ve never seen a good example where…

> No one argues against [...] deploy and orchestration tools.

People do argue against Kubernetes!

Re: Don't be a meat proxy

#732

All I can say is you're lucky that your meat proxies are still identifying themselves as such. I've had people forward AI responses … sans "Claude said". I'm quite literally talking to Claude via proxy, and I've caught more than one person pulling this stunt. It's a nightmare of negative productivity, though. Just why? And invariably the kicker is they still want me to solve their problem, whatever that might be.

It's ironic that your usage of "the kicker" invoked ai slop vibes even though I'm sure your post about ai slop was not itself ai slop.

Re: Don't be a meat proxy

#733

At my $work, people do this frequently, but instead of it just being insensitive, they have their personal Slackbot responding on their behalf. After I realized I wasn't even talking to a person, I've stopped opening their DMs.

Your response to them is understandable, but surely more communication, not less, is the way to go to fixing the root cause of this problem.

Re: Don't be a meat proxy

#734
Saying don't do it won't solve the problem unfortunately. Changing the review process so the session is tied to the code and the reviewer can ask the session/agent is the way, imo, and what we're doing at Chapter.

Re: Don't be a meat proxy

#735

Earlier quoted context omitted.

IQ gets manually recalibrated downwards when people get stupider so it's mean 100 by construction.

Hmm, who does the calibration, and how scientific are they about it? Can we check their work?

I am not too deep into the science of it, but this video gives a good outline about IQ in general.

https://www.youtube.com/watch?v=FkKPsLxgpuY

Re: Don't be a meat proxy

#736

One way to prevent obvious AI language from sneaking in text destined for other human beings is to ask the model to produce ASD-STE100 Simplified Technical English bullet points. This will result in a list of sentences that are clear and explanatory, easier to double-check, and convenient for the user to rewrite into a more readable format with a human voice.

Okay, but this doesn't really solve the problem of encountering a meat proxy. Now the proxies will be harder to detect because they are asd-ste lingo.

Re: Don't be a meat proxy

#737

I 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 keep cussing at it saying “don’t give me a wall of text ...” it just like eating tokens. It’s trained to eat tokens for anything. No matter what workarounds you use, claude.md/memory/skills what-ever you throw, after 2 exchanges it goes back eating tokens. I cant wait for an open model good enough like opus 4.8 where can control the gregarious factor

Re: Don't be a meat proxy

#738

Earlier quoted context omitted.

Kids, young folks, anyone reading: this is golden handcuffs. If you’re unhappy, make a change .

Well, I am reading it and I hope I manage. It's pretty scary to leave behind what I've excelled in all my life but it is the only way forward for me. So thanks for the encouragement :).

Lean into architecture design,

and being able to instruct a remote junior using what you’ve learned,

vs directly regurgitating your experience into code.

(or is that what you hate?)

Re: Don't be a meat proxy

#739
post #56

I 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…

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…

Oh man, this resonates. I feel like I’m starting to drown in an endless sea of overly verbose documentation that the originators themselves never read. If you ever have a question, they’ll just point you to the docs “they wrote.”

Re: Don't be a meat proxy

#740
post #687

Earlier quoted context omitted.

At my current job I just asked a coworker in chat if the reply was his or LLM. He quickly owned up and the incidence of brokered LLM messages in chat dropped signficantly. Unfortunately people are being encouraged to use LLM in docs, emails, and presentations so it's probably a losing battle.

We had an exec show how he was using AI to write interview feedback from his very sparse notes, in front of a few thousand people.

Don't you just love how, instead of making tradeoffs or prioritizing, we just do more, worse?
Post reply on HN