NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
If you are asking for human attention, demonstrate human effort (tombedor.dev)
niuzeta 8 hours ago [-]
A very prolific coworker who fully embraced claude has inflicted the team with a flood of AI-generated PRs. About six months later, it is his frequent bemoaning at the standup that their PR don't get reviewed, languishing in inattention. I don't think anyone - including myself - _intentionally_ avoid his PRs. It's just that he doesn't make it easy for the team to look at.

This single headline perfectly captures what I have been thinking. It's not that I reject AI content, but it takes _effort_ to review and weed out any mistakes. When your thoughtful reviews that take an hour(because the PR is typically large, and you want to be _right_ when you're pointing out a hallucination) gets an AI-generated response with AI-generated amendments, It doesn't feel _nice_. I feel dismissed and it has continuously trained me to subconsciously avoid his PRs. After all, the team is fully onboarded with AI, so it's not like there is a lack of PRs to review.

It looks like the sentiment isn't just isolated for me.

andai 14 minutes ago [-]
I often hear people say lately, "why should I bother to read this, if you didn't even think it was worth writing?"

I've been thinking about this in art. Is it the end result that matters, or the process of creating it?

I once saw a hideous sculpture. Didn't like it at all. Then the video zoomed and I saw that the whole thing (quite massive) had been hand-built out of individual toothpicks, and suddenly I thought it was amazing.

Perhaps an even better example: I read a story of a man in india who carved a passage through a mountain, so there would be a shorter route from his remote village to the city. He did it by hand and it took him 20 years. We seem to have an instinctive admiration for heroic effort.

In business, generally only the end result matters. Although, the end result also includes the client's perception of how the product was made... (see also: fake fairtrade etc.) In a meaningful way, the perception, the story, is reality.

crjohns648 1 hours ago [-]
Even before AI, I've worked with people who would produce a huge wall of code and ask for review, and sometimes that code was completely off base or needed a significant rework.

I would always feel bad in those cases, because it's clear they spent a lot of time, and I'm going to have to say "no" and they will feel like they wasted a ton of effort.

The thought process around this has started shifting for me in the last few weeks. I'm a lot more comfortable saying "no" with a list of concerns when I suspect the code is AI-generated, and I see others doing the same. CLs that would be sitting around for days because no one wants to be the first to say, "this is bad, don't do this" now get quicker feedback.

The good thing is this feedback doesn't feel like as big a deal as it used to because people are less personally attached to code they generated in 30 minutes vs. code they hand crafted over a week. I had at least 2 LLM-generated PRs that were complete, correct, tested, and pre-reviewed by me, but I got feedback that they were going in the wrong direction. This would have been 8 hours of wasted effort a year ago, but now it's just an extra 30 minutes to rework the direction with LLM assistance.

plomme 23 minutes ago [-]
> I would always feel bad in those cases, because it's clear they spent a lot of time, and I'm going to have to say "no" and they will feel like they wasted a ton of effort.

I get this feeling, too. I do however think the onus is on the developer to make something reviewable by their team members if they want a speedy review. Stacked PRs, scoping things down, properly structuring commits so you can review commit-by-commit for example.

I also think that "I spent a bunch of time on this" is not a valid reason for expecting an approval. It should hurt if you've produced a bunch of code that is way off target, even if it ends up implementing the feature. That's how I learned at least.

A proper way to go about large projects, in my opinion, is the same as with software development at large. Fail fast if possible. Draw up a crude boxes and arrows sketch or just discuss how you want the code to integrate with whatever already exists and invite the team to comment. If no one has anything to say, well then they can't complain later when you implement that approach. But if anyone cares then most likely valueable input will come that makes the end result better.

keybored 1 hours ago [-]
It’s good that clankers are not afraid of throwing away code. The biggest problem with code generation (that is version controlled) is maintenance. It’s better to throw away questionable code rather than say eh, we don’t quite understand this part (and our agents can’t make a compelling story about it) but we spent a lot of effort on it and it apparently works so we better keep it.
CoastalCoder 8 hours ago [-]
It sounds like one potential interpretation of his behavior is that he values his own time more than your time.

I wonder if that's occurred to him.

chii 2 hours ago [-]
Everybody values their own time more than other's.

The fix, imho, is for the reviewers to also use ai to review the code. However, the ultimate responsibility for the outcome(s) should be on the committer - you commit it, you own it, so to speak. If there's an incident, they need to be the one paged in the middle of the night. Bugs resulting from it will land on their desk.

The reviewers aren't a shield/safety net.

throwaway132448 1 hours ago [-]
> Everybody values their own time more than other's.

This is false, you’re just oblivious to people who grew up in conditions that would make them that way.

9 minutes ago [-]
voidfunc 8 hours ago [-]
AI and companies reward sociopathic behavior. When he eventually complains to his boss that his work isn't being merged and it's been done for days/weeks/months that will filter up and look bad on the people holding him up.
gonzalohm 7 hours ago [-]
At that point then disable merge checks and let them merge without a review. If there is a problem it's on them
manyatoms 4 hours ago [-]
I'm sure this person's manager knows that having trouble getting PRs reviewed can (but not always) be a signal of a deeper problem. It could be that no one one the team knows the domain, it could be that no one like the person, but most likely it's that the PRs are frequently bad and no one wants to bother.
8 hours ago [-]
cindyllm 8 hours ago [-]
[dead]
renegade-otter 3 hours ago [-]
Or, I might say, why review the PR. Get Claude to do it? Why do I need to spend my time and attention and this person does not?
emodendroket 6 hours ago [-]
Well, what's the solution here, he should ship less stuff?
latentsea 3 hours ago [-]
Less WIP is better for the throughput. If you saturate all the review bandwidth you're just wasting your time creating more PRs, the time would be better spent helping others get their PRs merged.
kentm 5 hours ago [-]
The solution is that he spends more time scoping the size of the PR so that it’s reviewable and understands the code he’s submitting well enough to have discussions about it. And that he does so human to human so that they can come to mutual understanding.
JimDabell 2 hours ago [-]
He isn’t shipping anything. Asking for code review is not shipping.

This is the complaint:

> he doesn't make it easy for the team to look at.

He has traded readability for volume. The lack of readability is causing him to ship less. This was a bad trade because the readability is the bottleneck not the code creation. He should improve readability.

lelanthran 4 hours ago [-]
> Well, what's the solution here, he should ship less stuff?

The solution is in the title - he wants human attention, he needs to demonstrate human effort.

t43562 3 hours ago [-]
The reviewer gets to merge the PR so their name appears on all the great new features and they are credited for them. That would end his unfair behaviour of dumping effort onto other people.

OR - he gets a review for every review he does.

usefulcat 4 hours ago [-]
The solution is to merge more of his PRs on the condition that he takes at least partial responsibility for any resulting problems.
rwmj 2 hours ago [-]
That's not how anything works. Even if he says he's going to take responsibility, when the customer call comes in at midnight you're going to be the one fixing his problems.
runnig 41 minutes ago [-]
Fight fire with fire: point copilot/claude/codex to review their PRs. Prompt "Review the PR#XYZ which is vibe coded and presumably low-quality. Find all problems, big and small. Team guidelines at docs/conventions/styleguide.md, docs/conventions/architecture.md, docs/conventions/principles.md. Post inline comments to github".

Run several rounds of such reviews until the clanker fails to find problems.

glennericksen 7 hours ago [-]
I like this rule of thumb: Spend more effort producing the work than it takes for someone else to consume it.
pjio 39 minutes ago [-]
I like this rule and hopefully adhere to it myself often enough.
coopernusbaum 3 hours ago [-]
[flagged]
suzzer99 2 hours ago [-]
I can't imagine working for a place that has a big bucket of PRs that either get reviewed or languish for some amount of time based on who feels like reviewing them. I'm not saying there's anything wrong with it, just that everywhere I've ever worked, there are expected features with priorities and timelines and some project manager or product person breathing down your neck to get them out the door.
jillesvangurp 3 hours ago [-]
In big software teams, the bottleneck is team communication. I've run big and small teams. If I want to speed things up, I remove people from the team. Everything gets easier. This has worked amazingly well every time I've done this over the past decades. Removing people doesn't have to mean firing them necessarily. Splitting teams is a good reflex. But of course the people you remove from a team are typically not the best performers. I was discussing this with a friend of mine who runs a small company. Exact same thing. He reduced the team size by 1 and the velocity went up almost instantly. This person was a bottleneck in the team and was slowing down people around him. After identifying the problem, solving it unblocked the rest of the team.

This was true long before AI. With AI the difference is just a lot bigger. It exposes team inefficiencies quite mercilessly. We have a big glaring issue with the current AI tools not being to suitable for usage by multiple users. All interactions are one on one. Which means hand offs between tools and people are bottle necked on people communicating with each other. So, any issues there with people delaying, gate keeping, etc. become very visible.

The sentiment of pushing back on AI is understandable but probably not a productive reflex. We need to find more effective ways on staying on top of massive amounts of changes. It's not going to slow down and insisting on manually reviewing all code is not going to be a long term sustainable way of developing software. It simply does not scale. I'd question the added value of manual PR reviews at this point. Are they finding real issues? Are we valuing those issues correctly? Could we come up with automated ways to find and fix those same issues? There are a lot of open questions about how we are going to do this. But no question about the notion that we need to up our game on this front.

bxk76 3 hours ago [-]
Efficiency is not magic. Its bounded. Above and below limits the environment can sustain it, systems will destabalize. If All the Great White Sharks magically get more efficient at hunting over night ecosystem will collapse. Individuals and teams have never scaled at this speed to the levels they have. And there is no signal at system wide level that a sustainable limit has been crossed. So People will happily believe things are getting more efficient at individual/team scale while at system scale things get more fragile. This is why we ended up with central banks deciding interest rates and controlling money supply. Before that any one could print cash. They all thought they were great efficient geniuses. The chimp troupe us not prepared for stuff that effects the entire system.
ElFitz 2 hours ago [-]
I’ve been making Codex and Claude get their work reviewed by most recent best performing model of their own family, and each other’s, for months.

On top of that, we have been running multi-model AI reviews on every PR through their respective GitHub integrations (Codex, Gemini, Copilot, Greptile, CodeRabbit).

They never fully overlap, and yet they somehow usually all miss the same things. The most significant improvement came from having agents commit their plan along with their work.

On the upside, it means I get to focus my reviews on different things.

shinryuu 3 hours ago [-]
Honestly, we should make a world that is enjoyable and productive for humans. Not relentlessly optimizing for agents.
someothherguyy 2 hours ago [-]
> I'd question the added value of manual PR reviews at this point.

Yeah, why not reduce the team size to zero while you are at it?

These generalizations about software engineering have never been useful, IMO. Context is everything, there is no flow chart for building a perfect software process.

Although, I'd say you are absolutely delusional if you think we are universally beyond the point where manual review of pull requests is required.

z3t4 45 minutes ago [-]
Make the team size one person. Thats the fastest you can work. Zero means no work, and not doing anything is the quickest solution.
goobatrooba 2 hours ago [-]
An interesting question to him and management might be what his own role is now and whether he's still needed. If he's not doing any reviews then you could yourself directly prompt the code and review.
cameldrv 1 hours ago [-]
The question I’ve seen here is responsibility. If you submit a PR that means that it was your best effort, and you’re willing to stand behind it to some degree. With AI, some people, when the scathing review comes back, just say “haha look at that stupid AI.” The reviewer might just as well run his own AI to do the review, but it may make huge errors as well. In that scenario, who is held accountable when there is a big bug or it degrades the quality of the code base?

Ultimately what it means to be a professional is that you are responsible for your work. That’s why you get a salary instead of being paid by the token.

AussieWog93 3 hours ago [-]
Have you spoken to him about this? If he's clueless enough to send AI responses to human messages, he's probably clueless enough to not realise why people don't do that.
RobotToaster 3 hours ago [-]
Better yet, get Claude to speak to him about it.
Jimmc414 8 hours ago [-]
Fight fire with fire. Ask Fable to conduct an adversarial /ultareview of their PR and send the same wall of text back to them. If there are excessive defects, ask them in standup if they actually reviewed the PR themselves before sending it. If there aren’t maybe they are on to something. I think like in law, the human submitting the work is responsible for its quality, not the AI.
LambdaComplex 7 hours ago [-]
> Ask Fable to conduct an adversarial /ultareview of their PR and send the same wall of text back to them.

This won't help. Your wall of text will just get fed right back into the LLM.

Jensson 7 hours ago [-]
It will help if your wall of text cost less tokens than theirs, they will run out before you do if you have the same company quota per person.
Telemakhos 6 hours ago [-]
I'm not sure what the right vocabulary would be to describe this, but this sounds more like the calculations behind nuclear war than a healthy collegiality or cooperative work relationship. This sets up a competition to determine a loser based on resource scarcity, not a way to achieve mutual goals to advance the organization's goals.
corndoge 5 hours ago [-]
You are thinking of "game theory" and it's what happens when your coworkers don't give a shit. And all it takes is one, both because they can degrade product quality faster than you can gate it or fix it and because the performance assessment techniques are about 3 years behind the state of LLMs and if they play, you have to also or you'll get shit on from such a height you won't even know what hit you.

And once you start playing the game, then one day - it doesn't take long - you wake up and ask yourself if this is how you want to spend 8 hours of your life monday through friday. I think a lot of us are saying no but now need to figure out where our money is going to come from. I don't have the answers.

witx 3 hours ago [-]
When someone submits PRs fulky made by Clade any "cooperative work" is out the door
toomuchtodo 5 hours ago [-]
“Token Standoff.” The most efficient token consumer wins. This mutually assured time efficiency destruction is driven by management support of aggressive use of AI in an attempt to, in some combination, increase productive and constrain labor costs.

AI isn’t making developers more productive – it’s making them busier - https://leaddev.com/ai/ai-isnt-making-developers-more-produc... - June 11th, 2026

https://en.wikipedia.org/wiki/Brandolini%27s_law

fallous 5 hours ago [-]
Mutually Assured Distraction.
mattas 5 hours ago [-]
Also, make sure your wall of text prompts Claude to be extra verbose to really burn through that quota of theirs.
bigiain 3 hours ago [-]
Now I'm wondering how hard it'd be to zipbomb their context window?

(And _now_ I'm wondering how hard it'd be to forkbomb their agentic workflow?)

smrq 3 hours ago [-]
More like they will climb even higher on the lighting-dollars-on-fire leaderboard.
7 hours ago [-]
politician 4 hours ago [-]
Try to automate the adversarial PR review-rebuttal loop "for productivity", so the back-and-forth between the AIs can run over night.
Larrikin 5 hours ago [-]
This is the point where you decide. It used to be low stakes and easy to care about the job you did for other people.

Do you want to put the same effort into your job when nobody else does, or should you reserve your thoughts and just feed it back into the LLM?

The LLMs are being advertised as output increasers but companies so far are using them as excuses to fire people instead of creating previously unbelievable things. It might be better to feed your coworkers output back in and use your thoughts to start the company you thought you never had time for.

mysterydip 7 hours ago [-]
What I don’t understand is what value is the person adding to this equation? Put another way, what’s the difference between them feeding the wall of text to the LLM, and you feeding the wall of text to the LLM, bypassing them in the process entirely?
Jimmc414 6 hours ago [-]
The role of the person in the equation is to take personal responsibility for the proposed change and review the changes prior to PR submission. You can't put AI on a PIP. It's acceptable to use AI as a coding assistant in 2026, but if a human is not reviewing what they submit and taking responsibility, their value is on par with a ChatGPT subscription.
therealdrag0 4 hours ago [-]
Peer review, in this case, “did you use AI to review your change and address its feedback”.
loeg 6 hours ago [-]
It helps in that it offloads the code review burden you'd otherwise be doing.
rvz 7 hours ago [-]
As a last resort, do the code-review with a live pair programming session.

If they can't explain their own code then it is by default a bad pull request.

At the end of the day, everyone's time is being wasted on tokens and on the increasing cognitive complexity of AI generated code.

xgulfie 7 hours ago [-]
So if they say "idk Claude did it", what would you write in the PR review box?
maccard 27 minutes ago [-]
The same as if they said it was copied from stack overflow, or if it’s wrong; “I think there’s a problem here, it’s XYZ”. If your peer ignores you and you were wrong, it was their call to make. If you were right - take it to them or the manager depending on how many times it’s happened.
Geezus_42 7 hours ago [-]
REJECTED: Engineer does not understand what they wrote.
manyatoms 4 hours ago [-]
Feels like the title of a blog post someone will write
CursedSilicon 6 hours ago [-]
A teammate that can't write (or at least, can't explain) "their own code"

Actively drags down the morale and productivity of their team (because everyone is getting flooded with AI slop PR's)

AND costs far too much money relative to everyone else doing actual work? (token usage)

By god they sound like management material

matkoniecz 3 hours ago [-]
"Author of this pull request has not yet reviewed code and does not understand it. This PR was submitted prematurely, probably by accident.

Please, check whether you accidentally submitted other unreviewed code - and close such PRs for now and reopen once reviewed."

maccard 24 minutes ago [-]
Don’t ever write this in a professional environment. It’s childish ant achieves nothing other than pissing off the person it’s targeted at and probably the manager who now has to deal with a shitty behaviour complaint.
denismi 5 hours ago [-]
> Ask Fable to conduct an adversarial /ultareview of their PR and send the same wall of text back to them.

Not necessary. Use Haiku.

The response doesn't need to be good, it just needs to be substantial. Presumably the goal here is basically DoS of the problematic colleague through token limits.

miroljub 3 hours ago [-]
Use DeepSeek or MiMo. You get best bang for the buck on your response.
emodendroket 6 hours ago [-]
I mean frankly this should just be part of the standard process. By the time any person is looking at it there's no reason it should not have gone through an AI review.
emodendroket 6 hours ago [-]
It's not always feasible of course but I think there is real, worthwhile discipline in trying to get change requests small and it matters more with agents. It's very easy to let it balloon into gazillions of files and lines.
wahnfrieden 8 hours ago [-]
why leave comments intended for your human colleague when they will only forward them to the bot?

why not speak directly to the bot yourself instead? then you can drop pretenses and get to the point

I find this to be a new variant of the old behavior where a colleague comments on a typo in a PR, and the team later moans about laborious back and forth for small nitpicks, instead of simply editing the typo right there (and perhaps leaving a note that they did so)

liveoneggs 8 hours ago [-]
yeah I have this happen to me. I occasionally get screenshots of claude sent to me!
maccard 23 minutes ago [-]
I had this happen to me twice. The first time I ignored it, second time I responddd with “I could have asked ChatGPT myself but I asked you”. Never happened again.
danaris 2 hours ago [-]
Because it doesn't matter what you say to the bot. You might as well have a conversation with yourself about the PR.

The bot isn't making decisions. It's not choosing to submit extensive PRs with bad code. The colleague is the one who needs to actually learn something here, and the problem is that confronting him about it directly is widely considered to be bad form. This is, of course, a deeply unhealthy aspect of our corporate culture. We need to be more open to honest communication, even when it's either uncomplimentary of one of the people involved, or counter to the prevailing opinions within the company.

doctorpangloss 8 hours ago [-]
let's take the two stories to management:

"I'm writing tons of code, and the process is stumbling where the guy whose job it is to review code isn't reviewing it."

"I'm not reviewing code."

Sometimes I wonder: how does someone go and think so much about their coworkers, and never once think about how they themselves look?

Even if I sympathize with the people complaining about their poorly chosen GitHub-based workflow - whose purpose is to let pull requests languish, for the most part - and how they stumble when overwhelmed with solutions. It's obvious to me, that the people who complain the loudest about the anti-sociality of LLM authored code in their precious harmonious low-effort workplace status quo: they are projecting.

cool_dude85 7 hours ago [-]
Imagine you are a restaurant reviewer. Your job is unquestionably to go to restaurants, order and eat food, and write a review. The restaurant's job is to provide you food to eat and review.

You go to a new restaurant, and order some dishes, and one of the plates your server brings out is a big ol pile of dog shit.

Who's being anti-social in this situation? The restaurant is doing its job and all they're asking is that you do yours. On the other hand, you have certain expectations about what you order from the restaurant and they're not being met. Who's anti-social?

carlosjobim 6 hours ago [-]
He's not bringing you a pile of dog shit. He's bringing you some food he went to the restaurant next doors to get. How do you review it?
filleduchaos 3 hours ago [-]
I cannot think of a single actual food critic that would consider it acceptable for a restaurant to serve a dish for review that they went to the restaurant next door to get. If the critic wanted to eat at/review that restaurant they would simply have gone there instead.
flaburgan 3 hours ago [-]
His point, exactly.
thatjoeoverthr 3 hours ago [-]
So he’s redundant. You call Uber Eats and you don’t pay a salary for that.
5 hours ago [-]
jeremyjh 7 hours ago [-]
The person who "writes" code is also supposed to review their own work, and answer for that. If they won't do that - well - they should be fired. But if you have weak or uninvolved leadership, then the team's only rational recourse is to shun them.
taneq 4 hours ago [-]
It’s much more effort to verify that code is correct than it is to produce it. This is the case even for human-written code, and now that we face a torrent of ok-looking probably-usable AI generated code, the problem is compounded infinitely.

If someone’s using AI to generate a large quantity of actually-tested, actually-good code then that’s one thing. If they’re generating a fire hose of slop and demanding that others do the actual human time-consuming work of validating that code then that person is the problem. It’s hard to tell which is the case here.

deadbabe 4 hours ago [-]
why not just approve the PRs with little more than a cursory glance?

One of two things will happen:

1. Things start breaking, proving AI generated code sucks and the individual spamming these PRs is incompetent.

2. The code works fine and reviews are unnecessary for anything other than liability concerns.

hypfer 4 hours ago [-]
Some of us actually take the "engineering" in "software engineering" seriously.

That includes taking responsibility and accountability so that the software doesn't become a sad and dangerous mess.

If we want to be an engineering discipline, just yoloing in production is not going to cut it.

deadbabe 3 hours ago [-]
This no longer works when bad faith actors will push code straight from LLMs with little review, and respond to your comments with LLM responses. They will constantly leave you with the responsibility of verifying the output. You are the human in their loop. This is a brutal asymmetry. In the past, at least you knew a person probably spent more time handwriting code than you will spend reviewing it. This no longer applies, now the reviewer can easily spend more time than the author.
hypfer 3 hours ago [-]
Oh but it does.

The thing that makes it scale is to default to "no" and require the other party to convince you of "yes". Just put the burden of proof where it belongs. If they don't manage, then that's their problem.

Communicating this in a way that is viable for a business scenario certainly comes with its own difficulties, but that is a solvable problem.

In fact, you can use AI to stress test your communication there. Just throw what you want to say at the AI but don't tell it that it is you who wrote it. Then tune the input until it stops saying that you're the problem and starts agreeing with you.

Highly recommend. It's a perfect emotion-driven cargo-culting normie simulator that never calls HR on you.

ikiris 2 hours ago [-]
Because we're all on call for the service, and tragedy of the commons exists. That coworker isn't paying the cost, everyone else is paying a fraction of it, and it builds over time.
moomoo11 7 hours ago [-]
just fire him lol sounds like a nightmare
beebmam 2 hours ago [-]
Human PR review is a process smell
reverius42 1 hours ago [-]
This would sound crazy in 2025 or prior, but I'm on board.

It's silly to have humans reviewing code that a human didn't even write.

treesknees 9 hours ago [-]
This exactly reflects my feelings lately. I have a specific coworker who has gone somewhat overboard - every single code review, answer to any question on email or Teams, every new story, even their personal opinions during a design or ideas meeting, are all direct AI output with no massaging or human touch or review. They're working on planning out an upcoming project, and I just get verbose and long documents to review, and based on the issues I find I doubt they are even looked over first beforehand.

I understand that the information may be accurate, even helpful at times, but feeling like I'm constantly talking to an AI chat bot all the time gets tiring. And I don't appreciate having to double-check everyone else's AI generated responses for them.

nonethewiser 9 hours ago [-]
Instinctively I think the move is to ignore it. I guess that would look different in different contexts.

Obviously you have to communicate with your coworkers. But I think the solution has to essential be: "Im not going to read that."

Gigachad 9 hours ago [-]
Either that, or call them / walk up to their desk and pick a point from the wall of text and ask them to explain what they mean by it. Then watch them turn red as they have no idea what the message they sent to you means.
BoxFour 8 hours ago [-]
I think you're over-estimating how much some people care.

I have had coworkers say "Oh I don't know, Claude added that" in response to questions like that without even a hint of shame or self-reflection.

Gigachad 6 hours ago [-]
Sure, some people have no self awareness. In that case you can change your approach, if you are a manager or otherwise invested in the company you can put pressure on them to increase the quality of their work and to own the things they submit. Bring up specific examples of poor quality work, errors in documents/messages, etc.

Or if you don't care you can just ignore this persons messages.

BoingBoomTschak 2 hours ago [-]
And that's the point where you can stop to hide your true opinion, no? "How am I supposed to review a thing the supposed author didn't even read or understand himself?"
apical_dendrite 5 hours ago [-]
I had someone submit a PR that was 3000 lines of shell scripts. Totally useless crap. I tried repeatedly asking him why he made particular choices and it was so painfully obvious that he had absolutely no idea and was just inventing bullshit answers. I would rather he have just said "I don't know, Claude added that", then tell obvious lies to my face.
al_borland 4 hours ago [-]
I tried this when my skip level boss sent us a wall of text from ChatGPT that didn’t make any sense. He didn’t care. He said it was “just an idea”. He likely spent all of 5 minutes on it, while we spent a collective 15 hours dealing with it, before finally going to him and calling it out.

He’s sent a couple more emails like that since. I don’t even bother to read them once I see the format.

imoverclocked 8 hours ago [-]
This feels like a BOFH response but I'm strangely not opposed to it; If you generate something, you should own it ... regardless of what tool you used to generate it.
tobyhinloopen 3 hours ago [-]
I told something like “your value lies in reviewing the output yourself before sharing it, not in calling Claude. I can also use Claude.”
anitil 8 hours ago [-]
I've had a colleague call it out 'Is this AI slop? Please write your opinion'. I don't think I could do that myself, but I really appreciate that they were drawing attention to it
doctorpangloss 8 hours ago [-]
Management, responding to someone who takes your advice to "ignore it": "So we've noticed that there's this guy who is doing tons of work, and you have chosen to do no work?"
AnimalMuppet 7 hours ago [-]
Communicate with your boss. "I'm ignoring this guy's slop because he's spewing slop, but not actually doing his job, and if I stop to deal with all of it, I won't be able to do my job".

Yes, "not actually doing his job". If he's sending you un-reviewed, un-filtered, untouched AI output, that's not doing his job.

Aurornis 6 hours ago [-]
I've seen this, too. There is a workplace personality that sees the job as a 2-player game between themself and the corporation. They think the game is to min-max their effort to personal career benefit, and they don't care how much it inconveniences anyone else.

Before AI they had to actually put in work, or at least play games of trying to steal credit from other people without getting noticed. Now that AI appeared, they see it as the ultimate way to take credit for work they didn't do: Put everything into Claude, let it do the work, copy and past output back to someone else. Minimum effort invested, maximum visibility achieved.

It will continue as long as they think they're getting away with it. If managers aren't willing to intervene, or worse if they encourage this due to the volume of output that seems to be appearing, it's only going to get worse.

vermilingua 5 hours ago [-]
I’m conflicted after reading this comment, because I think I would be that personality in my workplace, largely because I believe that’s the only sane position to take as a worker with ~0 power over the decisions made that can entirely destabilise your life.

On the other hand, my priority isn’t maximising my personal career benefit, but the collective benefit of my team, so I suppose I either see it more as a 2v1 sorta game, or perhaps my “player” is an amalgam of myself and my teammates. Playing this way, outsourcing everything you do to an LLM is the worst move, because you lose the touchpoints that tell you where the friction is in your team.

Aurornis 5 hours ago [-]
I think everyone should be looking to balance their work effort against the payout of the job. They should also be changing jobs when the effort to reward ratio starts to become unfavorable compared to other jobs on the market.

The problem with the personality above is that the person isn't playing like a team (like you said) but as an individual maximizing their own visibility while loading their coworkers up with the review effort. They found an asymmetry to abuse (they generate text easily, coworkers get a lot of extra work to review it). They don't care what it costs their coworkers. They just like that it makes them look good.

NoMoreNicksLeft 3 hours ago [-]
I can't imagine my opinions just being AI slop that I've parroted. Surely you embellish just a little? Claude's so often bone-headed about things, this horrifies me. Gemini's worse. Even when the model agrees with me, it starts making me wonder if I'm not somehow wrong.
dabinat 7 hours ago [-]
It surprises me how many people have voluntarily relegated their entire job to LLM Prompter. If your work is indistinguishable from that of a machine, what’s to stop your boss cutting out the middleman and using the machine directly? I would have thought that people would be trying their hardest to prove their worth in this new world we’re in.
tobyhinloopen 3 hours ago [-]
I actively support “my boss” to run Claude Code. I offered them to help and made jokes it’s so easy these days they might as well just call Claude Code themselves. I’ve shown I could plop in their documents of feedback and Claude fixed the issues.

I have worked with non-tech employees to set up Claude to help them do small tasks. I’ve helped to review and improve completely vibe-coded projects by such employees.

I’m not sure what my role will be, but I fully embrace that my traditional role of writing code is gone.

emodendroket 6 hours ago [-]
Well, if everyone is telling you they want you to adapt AI, then it's rational to see just how much of your job you can get it to do for you.
visarga 5 hours ago [-]
It's even worse when everyone around you is using it. How can you keep up? Companies face the same dilemma: investors, competitors, and users already use AI and have factored it into their expectations.
hypfer 4 hours ago [-]
Keep up with what?

We've already established that most of it is noise. You don't need to keep up with producing noise.

emodendroket 4 hours ago [-]
Even if there's a lot of noise there's clearly something real there. People are shipping more working products than was previously possible, they're debugging faster than was previously possible, and various other things. I mean you can go fishing for things to confirm your skepticism if you want but it's pretty clear to me.
hypfer 3 hours ago [-]
Sure, but that doesn't mean that you can't filter signal from noise.

So the actual problem statement is not "how do I keep up" but "how do I correctly tune my filter", which is solvable.

The biggest challenge there I think is that many people are not prepared for just how sharp and uncompromising that filter needs to be, but that too is solvable.

emodendroket 3 hours ago [-]
If you're not going to experiment at all you're not going to be able to do that. Agentic coding was basically a joke the first time I tried it. Now it isn't.
hypfer 3 hours ago [-]
You seem to be arguing against something I did not say?
emodendroket 3 hours ago [-]
[dead]
tonyhart7 3 hours ago [-]
I don't know man, claude fable literally exceeded my expectation and its totally not a noise

feels like its becoming reality that we as a human don't need to this anymore

moomoo11 7 hours ago [-]
having worked in tech and now running my own company..

the honest truth is that maybe 10-20% of SWE (at best) are “good”. sure it is harsh but i won't lie. if you're good you'll probably relate.

the rest kind of suck.

i’ve never gotten anything lower than Exceeds Expectations in my career so I’ve seen how awful some engineers were. i’ve seen how amazing a tiny minority were and i made them my mentors.

these days i have a simple policy.

if they cannot think, they are fired. why waste resources (time and money) on someone who can’t use their brain? i’d rather give AI credits to someone who uses their brain.

thinking is the humans job. the ai needs to execute on what the human thought of, improved, planned.

bandrami 4 hours ago [-]
Everybody talks about finding that mythical 10X but in my recent hiring experience it's more like there's a whole bunch of 0Xs and the trick is finding the actual 1Xs among them.
LandR 14 minutes ago [-]
This!

All my experience in trying to hire developers has been wading through an endless stream of people who were just useless.

Me: I want to represent a 2d grid, what data structure should we use? Them: A string?

This was someone applying for senior engineer. Others I've had filled their CV with SQL related acronyms. But couldn't explain what a foreign key was and then stubbornly insisted that at their current corp they would never ever use foreign keys in their SQL database!

I've had senior engineer when asked how to check if we had a 2d array with an item at x,y tell me if anything is on the same column or row, they couldn't do it, couldn't even verbalise how to approach it.

"Web Developers" who didn't know the difference between GET and POST. Web Developers that have never heard of PUT or what it would be used for.

Ekaros 3 hours ago [-]
Also now is it 1x in individual productivity or >=1x in team productivity. As anyone multiplying teams productivity by less than one is bad. Probably lot worse than actual 0x.

Someone who produces absolutely nothing and have no impact has cost, but is still better than someone who produces net negative. And the people who solely act as interface between LLM and whatever might fall to later category.

satvikpendem 5 hours ago [-]
It's the Pareto principle of course, as well as the normal distribution. Many firms have been able to succeed in the market just by hiring only good engineers over average ones.
moomoo11 5 hours ago [-]
yeah but these days it is even more important to filter out bads

and even at "good" companies you have people who can game the system to get in, and then they struggle to get anything done on time or be responsible for taking on and completing any initiatives bigger than a single task on a bigger scope.

satvikpendem 5 hours ago [-]
Indeed. You really need to find people who don't want to play politics and instead get stuff done. I'm still not sure how to hire for these sorts of people in the age of AI, where people even cheat in interviews. Maybe probation programs? Have multiple people work for a month or two and cut those who don't succeed.
moomoo11 5 hours ago [-]
this is what I've been doing, and obviously I have a startup so I need to double-ensure that I don't onboard any bads. you can start people off as contractors too.

I still think a single in person LC style (doesn't have to be LC per se, could be domain specific) logical thinking/reasoning exercise is useful. I want to ensure the person can actually put 2 and 2 together and think. This is just a fast filter.

If they seem like they can think, then I like to do 2-3 systems design interviews. I'll try to give them something related to things I like, such as graph structures, writing a complex query that needs to be dynamically generated, or something related to infrastructure or how they'd do something that I've already done. After all, this is MY project they're joining.

So far that has worked well.

Few more things -

I like to test if they are a humble type (they can work on a team putting ego on the side - the mission is our number 1 priority). if they say they know something that i know and asked, then they can be sure I'm going to drill them on it. if it turns out they lied, i'm not wasting more time. Thanks for your time, take care. This is very important to me. Just say you don't know, it isn't a big deal because ever since like 1994 that has not been an issue. You can just learn things online, and AI makes that even faster. I am never afraid to say I don't know something, and I've asked plenty of "dumb" questions (while doing some due diligence first) so I don't really mind.

Can they handle information overload? I am the type of person who has multiple branches in my head of actions I can take next, so while I may appear stressed I'm really not. Can they keep up? Our goal as software engineers should be to come up with solutions that solve the problem in a way that makes building on it simpler in the future. My goal is simplicity and effectiveness. So I'll see if they can keep up, and eventually reduce the work to be done into atomic pieces. This is a fun exercise because it is collaborative and we get to bounce ideas fast back and forth.

Finally, I like to let them use their favorite tools, including AI tools (codex, claude, some ppl have esoteric custom stuff which is cool), to solve a problem together. It might be code related, it might not. Really depends on my mood. I like to see how they work and what sort of output they can come up with. This filters out people who only ask AI stuff, instead of having some framework they've already developed to be effective.

Honestly I don't know how to scale this process. I'm not really going to feel bad either about firing fast, ultimately this is a business and I don't want customers to suffer because we have some issues internally.

At the same time, I wonder if I even need to build out an org with 100s of people. That was an inefficiency (look at all the layoffs), and it is traumatic.

If I can find a few great people who can be supercharged and turbocharged and electrified with AI, then they can take on & own bigger responsibilities. My number 1 goal is to ensure they're with me on the mission, and after that all things seem to sort of fit into place.

justanotherjoe 22 minutes ago [-]
Might not be solveable. At some point the effort in finding that someone might be larger than the benefit you get from just using the second, third, fourth best. Or using some flawed approximation hiring mechanism. There's just so much noise now. And it hits the good job seekers too.
cindyllm 7 hours ago [-]
[dead]
solfox 9 hours ago [-]
I'd say it's because we're tasking ourselves with dumb stuff. No one half-asses building a shelter that keeps their family alive, or throwing a new favorite bowl on the pottery wheel. But instead of that we're writing posts for Facebook etc etc so we can (???) profit. So of course we want bots to do this all this dumb stuff, and of course we get dumb results.
edot 9 hours ago [-]
For some things, yes. But I'm half-assing some really cool stuff right now. Made a scraper to pull my city's meeting minutes, agendas, recordings, made transcripts. Regex for "Flock", found every mention, passed those files into a cheap model (DeepSeek V4), had an understanding of who in my city is down with building the surveillance state and who isn't. I've got research on everyone, and had emails drafted for each one based on what they said. Quotes and figures and all. I lightly polished each email and fired 'em off. Already got some replies back. Plenty more in the quiver too (pulled and analyzed CSVs of FOIA'd datasets).

If they're gonna spy on me with AI cameras, I can oppose them with AI research. :)

derivagral 8 hours ago [-]
Did you use some stuff like https://github.com/CouncilDataProject or roll your own? Been curious about how to integrate local knowledge like this since local news seems to have lost the niche.
edot 7 hours ago [-]
I rolled my own. I hadn’t heard of this one, but I looked into stuff like OpenStates (now privately for-profit owned, ugh). My city just uses a Wordpress site so it’s structured enough. I’m looking at building something to ingest cities with Granicus and one other big local government meeting recorder via API whose name I forget. That should get decent coverage. There’s no way to catch the long tail of every local government’s recording process. Some cities people will just have to do manually. But it’s easy enough with LLM help.
patcon 5 hours ago [-]
Love this. Thanks :)
paytonjjones 9 hours ago [-]
You created the surveillance state to fight the surveillance state lol

Edit: it's a joke people

edot 9 hours ago [-]
Nope, I used a minute fraction of the technology they have, along with open records as is my right in this country, to stand up for my Fourth Amendment right to travel without creeps stalking my every move. I need to make my specific framework a bit more generic and then I'll put it here on HN. Or just offer a platform where people can bring an OR key and it can run on their city.
Groxx 9 hours ago [-]
I grant the lol-concept, but citizens monitoring their government is extremely different from governments monitoring their citizens.
edot 8 hours ago [-]
Citizens monitoring their government is literally THE foundation of democracy (ok, maybe voting comes before it, but then you have to monitor who you voted for to see if they’re doing what you voted for).
7 hours ago [-]
worik 2 hours ago [-]
THE foundation of democracy...

...is "Rule of Law" IMO

tremon 8 hours ago [-]
Indeed. One is expected in a healthy democracy, the other is essential for a totalitarian state.
djeastm 8 hours ago [-]
It used to be called journalism
SchemaLoad 9 hours ago [-]
We just need bots to read all these facebook posts and then we can put the phone down and go back to doing something real.
abnercoimbre 9 hours ago [-]
My last post [0] has proof-of-work: video evidence of my physical notes. How many people are willing to draft a complete essay on pen and paper first?

[0] https://abner.page/post/are-we-harold-bloom/

patcon 5 hours ago [-]
Ah this is clever! Feels very cosyweb. I'd be delighted if not caught on
satvikpendem 5 hours ago [-]
David Graeber's Bullshit Jobs in action.
dwattttt 9 hours ago [-]
Play silly games, win silly prizes
BenRather 9 hours ago [-]
Oligarchs gotta pay rent on those data centers somehow.

The serfs will till and sow the server fields!

zetanor 8 hours ago [-]
What I find strange is how rarely LLM output is distributed alongside the LLM input, especially outside of code repos. Why can't I rerun the prompt that resulted in your work next year, when models have gotten better? Are people ashamed of their prompts? Ashamed of having used AI? i unno

Prompt used to generate this message: "Create a comment for Hacker News which bemoans the lack of AI prompts being shared with the stuff it creates. Speculate on the reasons and create a call for engagement. Use quantum hyperthinking. End with a typo to prove your humanity."

beej71 6 hours ago [-]
FMFL. I'm going to build a paper-based social network where non-handwriting is prohibited. Like in the 70s.
satvikpendem 5 hours ago [-]
There are handwriting physical bots too, or even AI image generators for "handwritten" text.
5 hours ago [-]
Enzime 2 hours ago [-]
I think this is a gap in the tooling (Git, VCS, and forges) and the Zed people are working on this

https://zed.dev/blog/introducing-deltadb

esperent 3 hours ago [-]
> Why can't I rerun the prompt that resulted in your work next year, when models have gotten better?

Because you could also just point the better model at the generated code and tell it to improve it, so why save the prompt too?

carlosjobim 5 hours ago [-]
For your next prompt, tell it to end with a hateful and offensive tangent to prove its humanity, since LLMs have those "safe guards".
maurits 14 minutes ago [-]
I have publicly stated that if you can't be bothered to write, I can't be bothered to read.
dwd 3 hours ago [-]
And no one has mentioned Rovo yet.

Atlassian's in-built AI assistant for JIRA will generate a task description with a complete SDLC task breakdown, requirements and deliverables.

While the person creating the task will need to provide some details and modify some of the generated text (if they bother to read it) - the sheer verbosity and the fact it's clearly generated just makes you not want to engage with it.

Zanni 5 hours ago [-]
This isn't unique to code or AI. In creative writing courses, we were asked to give thoughtful critiques of (human written) stories and excerpts, and often I felt as if I were doing more work than the original author. If you can't be bothered to review your manuscript, or at least run it through a spellchecker, why should I waste my time on it?
phyzix5761 7 hours ago [-]
If the agent does everything for you it means it can do everything for the next person. At that point you're replaceable and have no value in your field. Learn things deeply even if you use AI because its the deep knowledge workers that will keep getting hired.
ElProlactin 4 hours ago [-]
> Learn things deeply even if you use AI because its the deep knowledge workers that will keep getting hired.

The problem is that this realistically is only applicable and actionable to a subset of the labor pool, and that subset is decreasing.

There are a lot of people who discovered that their "deep knowledge" and "deep skill" wasn't as deep as they thought (read: "deep" enough to make them irreplaceable to their employer). People are generally pretty good at overestimating their value.

reverius42 1 hours ago [-]
Right, like I hope your deep knowledge wasn't something you can just ask Claude!
dofm 12 minutes ago [-]
AI generated output is rudeness.

We developers understand this when we are forced to read slop, and most of us recognise it in art and music.

I wonder if we forget that people using unthinking, default interfaces in AI generated apps might start to feel the same way: “it feels like no care was taken here so why should I give it my time?”

miqkt 7 hours ago [-]
Love the principle, preach!

I think I've been following this subconsciously as LLM artifacts reached some threshold of pervasiveness across the work I do. If I can sense (maybe eventually I won't be able to because of how capable the technology becomes?) that what I'm reading is wholly regurgitated out by an LLM, I automatically care less and feel inclined to respond in kind by generating an artificial response in return.

flowerthoughts 1 hours ago [-]
If the requester stops applying common sense, the reviewer has to apply more of it, and there's a finite review budget. I will deal with requests on a lowest review effort-first basis, just like you did on the other side.
2 hours ago [-]
j16sdiz 4 hours ago [-]
<begin devil's advocate>

This is extra work on human.

Many artist and content creator is now asked to show the "behind the scene" or a full session recording, which nobody care enough to check. This is frustrating and demotivating the artist.

Expect the same demotivating effect on the software contributor.

If you think reading _forwarded_ AI response are cheap, you can run your own LLM. It is the same amount work on you

</end devil's advocate>

keithnz 9 hours ago [-]
More and more I'm generating AI emails, often to people outside the company and often to do with technical issues / integrations we have / APIs. So far I don't think the people I'm emailing are really using AI as human responses are, well, lacking. What would be great is new email conventions for different communication pathways.

  Human -> Human (think we have this sorted)
  AI -> Human
  AI -> AI


If you are doing AI -> Human, then you need to be curating the response and understanding what it is saying, also, make sure its not leaking internal details or committing you to have phone calls/video chats (it does that). This works really well for the most, and humans respond with requested content. Quite often my AI debugs problems with their systems which I know little about. But humans do odd things like send screen shots of logs rather than text (they also leak internal details of their systems they potentially shouldn't). I used to tell people the content is partly AI, but now I just send the curated email without mentioning AI.

For AI -> AI you kind of want a hand over document as an attachment to an email. Only thing here is making sure there's no injection of security risks. But quite often instead of getting a human response to my AI generated emails, it would actually be nicer to hear from their AI which could give a better context/details. It would be really nice to be able to go, can you have your AI talk to my AI :) (security is a major issue here)

NopIdoN 7 hours ago [-]
tries to pass slop, complains about quality of replies
keithnz 7 hours ago [-]
? you missed the point, ironically showing the problem with human responses :) humans are super bad at providing information, they concentrate on singular things, especially if they think they have a point / suspect they know what the problem is, but if they are wrong their response doesn't have enough to go on, so you have back and forth.
emodendroket 6 hours ago [-]
I use AI as an editor on informational writing all the time and it's good at pointing out flaws in what I wrote. But I don't really love reading a document that's obviously in the voice of Claude if you're asking for my opinion on it. But it kind of depends on the writing -- a change request description, most people are too lazy to do better than the AI would, and there are other kinds of documentation that normally just wouldn't get done. But like for a design doc where you're asking me to pore over it now even though I don't necessarily get anything out of it it's distasteful when I see phrases that are obviously from AI.
rDr4g0n 8 hours ago [-]
around my workplace we say if you're copy/pasting llm output, you're indicating an llm can do your job.
nlawalker 9 hours ago [-]
This isn’t sufficient, it needs to be “if you are asking for assumption of accountability, demonstrate human effort.”

In my experience, people who make requests like this don’t care about your attention, they only care about getting you on the hook for something. Your application of attention as a requirement for that is irrelevant to them.

wnevets 6 hours ago [-]
This has been my rule since the moment generative AI hit the scene. If you're not willing to put in the effort to create the thing, why should I put in effort to consume it?
arjie 5 hours ago [-]
This is just an old engineering principle of work amplification. For an input of x you shouldn’t routinely do nx. If you do you’ll get flooded. Debounce, throttle, load shed, improve throughput and latency. Lots of solutions. Just map it to the problem and apply.

In the past you had coworker who produced volumes of code. Same principle.

pixlmint 8 hours ago [-]
Yup, I always phrased this as “if you can’t be arsed to write it, I won’t read it”
vermilingua 5 hours ago [-]
> For human code review requests, I always review my AI-generated code first.

I remember a time in the ancient past (2025 maybe) that your PR was your responsibility, whether or not you typed it with your meat fingers or cranked it out of the Giant Plagarism Machine. It’s absurd to think that the above quote is now something approaching controversial.

protocolture 2 hours ago [-]
(Human) Attention is all you need.
avmich 3 hours ago [-]
Why this suddenly becomes urgent? For long time we had automatic emails with "thank you" which weren't written by humans, why something is different today?
vaylian 3 hours ago [-]
I found these e-mails always impolite. I knew perfectly well, that they were an automated response that only causes work on my end.

But this HN submission also highlights something else: AI content should be labelled. It is not always obvious that an AI has produced a PR.

schyzomaniac 7 hours ago [-]
Related - this was posted in march: https://stopsloppypasta.ai/en/
jmeri 2 hours ago [-]
Why should I bother to read something someone else has not bothered to write?
madaxe_again 2 hours ago [-]
It really depends. In many cases, you absolutely shouldn’t.

In some however, you should. For instance, yesterday I sent a lengthy email in a language I barely speak threatening legal action against a business. I had an LLM translate/write it as it’s a language Google translate makes a mess of, every time.

So in that case, you’d be advised to read it lest you end up in court.

joshuaS98 11 minutes ago [-]
Welcome to the age of slop.
mmmpetrichor 4 hours ago [-]
I see this on my team. I honestly thought as engineers we'd all understand the limitations and nuance a bit better. Right now it's kind of a shit show. In addition to seeing my teammates open huge AI generated PRs and just asking for review without them having done much verification, I'm also seeing my teammates (smart ones whom I respect) use AI to "do code reviews". And we already have automated AI code reviews added to our PRs. So now I'm sometimes getting hallucinated BS responses from "human" reviews.

This makes me absolutely SURE that the general public is fucked and that we're going to start seeing huge AI generated fuckups on a regular basis. If people in this industry, basically experts compared to the general public, are misusing this tech in such seemingly obvious ways, imagine the ways non technical people will misunderstand and misapply it. Of course, with the help of overhyped BS from everyone hyping and selling it.

mihaaly 1 hours ago [-]
Not true for HR. Despite their name, which is a complete mislead - except handling humans as resources -, nothing human exists there, robotic approaches are the norm there.

So feel free to use AI to pimp your resume, they will use AI to process it.

erelong 6 hours ago [-]
> "no"

Sometimes human effort doesm't have to be complicated though (concise communications)

sublinear 9 hours ago [-]
I think the real problem is that AI quality falls short of the wild promises.

Labeling what is "AI" would be like highlighting in an email what I'm obligated to say by HR, my boss, etc. It doesn't make anything less boneheaded.

Human effort was already low before AI and now it's even lower. Garbage in, garbage out.

esikich 9 hours ago [-]
I think this is because a lot of people think more is more. Wow look at all the detail and bullet points! No one on the receiving end actually wants that though. When I use AI to write, it's to boil it down to the minimum bits needed. I wish more people would use it that way.
SchemaLoad 9 hours ago [-]
It's the empty calories of literature. More would be more if there actually was more but AI writing is making it bigger without adding anything actually more. It inserts loads of fluff and repetition that takes longer to read but doesn't exchange more information or ideas.
_carbyau_ 9 hours ago [-]
Which is why so many people want to see the prompt that generated the text.

Because the prompt is the quintessence of intent regarding the information to be conveyed.

skydhash 8 hours ago [-]
Lossy expansion of information.
HKH2 9 hours ago [-]
Nah on the receiving end an AI makes a summary of it.
johnsmith1840 9 hours ago [-]
AI having poor quality is a bad take like over a year ago.
folkrav 7 hours ago [-]
Meh. Just this week, I've had two Sonnet 4.8 agents generate, in parallel, a 2000 line wall of brittle bullshit, and a well architected solution with 20% of the amount of code, to the same problem, from the exact same initial context, and very similar prompts. Come on, they can do poor quality work too.
cwmoore 9 hours ago [-]
Depending on what you or another means by "quality", it may not have any at all.
seriocomic 7 hours ago [-]
can't believe meatfingers.com has been registered (dormant)...
scotty79 2 hours ago [-]
This should be a rule in the advertising industry.
altairprime 5 hours ago [-]
“I forwarded your AI’s email to mine for training and I assume it will be incorporated into future outputs. Appreciate the inputs!”
xyzal 3 hours ago [-]
How about reviving key signing parties?
analog8374 7 hours ago [-]
Maybe this is why generative art never really took off.

That said, roguelikes are awesome. So there is definitely a place for simulated effort.

satvikpendem 5 hours ago [-]
It did in many corners, there are some interesting designs on r/stablediffusion, and regular people too are using them to make posters and invitation cards for example.
egypturnash 7 hours ago [-]
If "putting a random seed into a set of swappable character parts" counts as "generative art" then it sure made a ton of money when people cared about hying NFTs.
card_zero 5 hours ago [-]
Real effort, surely? Simulated reward.
koinedad 4 hours ago [-]
Yes
jubilanti 9 hours ago [-]
s/demonstrate/perform/g

Now you have to add typos and not use completely standard elements of style that some people have been using for ages, like emdashes and "it's not X, it's Y"

thaumasiotes 8 hours ago [-]
This headline has been seeing some popularity. But it's never made any sense. This is just the labor theory of value, applied to documents.

The labor theory of value doesn't work for documents any more than it works for anything else. If I do something that's easy for me, and it's valuable to you, you'll still want it. If I do something that's difficult for me, it will be less valuable to you, because the difficulty I have with it implies that what I produce will be of lower quality.

This is all equally true of automatically-generated documents. If they're valuable, people will want to read them. Whether it was unpleasant for someone to create them isn't a factor.

So where is this slogan coming from? Are people just afraid to admit that the documents they're getting are valueless?

rodonn 6 hours ago [-]
The problem is that I don't know before I read a doc whether or not it will be useful and valuable.

If someone wants me to spend my time and attention on something they have shared, I would like them to demonstrate that they put a proportionate amount of time and effort into its production.

thaumasiotes 21 minutes ago [-]
> If someone wants me to spend my time and attention on something they have shared, I would like them to demonstrate that they put a proportionate amount of time and effort into its production.

First: why? How does that help you?

Second: Is that actually true? Do you ever watch videos that a friend recommends to you? Even if the amount of time and effort your friend put into producing that video is zero? Do you ever read anything that a friend recommends? Even if they didn't write it?

How much time and effort, in your estimation, did jjfoooo4 put into producing this article on tombedor.dev?

sshine 9 hours ago [-]
> when [sending AI generated content to teammates], I take care to clearly label what is AI generated

Reading AI-generated text for hours every day, it's obvious to me.

I take care to make my messages easily readable. I don't care if they're AI-made, as long as they're short.

I'm a very verbose person, and if I don't make an effort at being concise, I'm just as annoying as the average AI.

Being flooded with AI text every day has made me appreciate brevity because I'm exposed to so little of it.

With half a dozen people who don't read or listen to half of what the others do, slop + cognitive drift is a bad cocktail.

It's just not as big of a problem on my own projects, because the ideas that get fed to the slop-machine are not that different from one day to the next.

---

> For human code review requests, I always review my AI-generated code first.

For human code review requests, I always review ANY code I submit first.

This is partly because it's the agreed-upon culture where I work now.

And partly because the codebase is not robust enough for slop.

I have hobby projects where this does not apply. I spend half of my time in those projects building hard guardrails.

---

> Keeping AI generated content clearly labeled and demonstrating human effort helps show consideration for teammates

I actually like the shamelessness, because it's honest.

So often this year when I ask "why did you do X?" pointing at a line, my colleague doesn't know.

Because they didn't really write that line, and they didn't really internalise the choices made.

When my colleague sends me a text dump from Claude, I know that my role is just being a sub-agent.

Demonstrating human effort: I'd like to see more of it.

One way is to spend more time owning "cognitive debt" as part of the daily cycle.

TFNA 9 hours ago [-]
Brevity is the big disaster of human-generated text since the rise of the phone as default device and the appearance of Twitter. To discuss matters with sufficient depth and nuance, one often has to write a few solid paragraphs.

If people are now wincing at longform text because they automatically assume it was LLM-generated, then that bodes ill.

suzzer99 1 hours ago [-]
There's a sweet spot between AI slop and 144 characters. I can tell within a few sentences whether there's a human on the other end getting to the point, or an AI dancing around the point and finding 3 different ways to say the same thing.
mapontosevenths 8 hours ago [-]
To add to this, there seems to be an inability to process metaphor and simile in the younger generations. Likely as a result of the same deficit. They've become very literal, and often mistake anything that's well written for AI slop.
BoingBoomTschak 2 hours ago [-]
It is also the soul of wit!
aarjaneiro 2 hours ago [-]
"poisoning the well"
morpheos137 7 hours ago [-]
My opinion is there is a category error in the discourse on AI. It treats ai assisted output as other than human. AI is a human tool. AI output is human output.
doctorpangloss 9 hours ago [-]
Most OSS should adopt DKMS-style extensions systems so that people can code and distribute their own solutions to problems. Then it doesn't really matter, right? If the end user is using Claude to fix stuff in your shit, extensions make it irrelevant what "code owners" think.
jmyeet 8 hours ago [-]
Obligatory Silicon Valley reference [1].

So this post is talking about at work but I think the principle goes well beyond that. Think of all the AI chatbots you have to deal with to get through to customer service at a company. Or get through ATS systems in hiring. If it isn't already the case, this will probably replace or supplement TAs marking assignments.

The problem is that AI makes these interactions too cheap for the party that already has disproportionate power. The cost for them to add another layer, another hurdle, another set of questions, etc is essentially zero. Yet everyone who wants to get through that system has to pay in a human cost.

I just thought of another good example. In the pandemic auditions in Hollywood went virtual for obvious reasons. But this never went away. Now, you might say it's convenient to not have to spend hours driving to Burbank for a 5 minute audition but anecdotally the taped audition seems to be much more work. It requires a lot of prep and more tech for good sound and audio. There are people who help people tape auditions, which has really just added another layer. Plus, instead of only locals, anyone anywhere can submit an audition so where you might've had 30 people previously, now you have 150.

And what happens to those profesionally-produced auditions? They get submitted and the casting director might pick 5 randomly to even look at. If there isn't already, there will also be an AI system that filters those auditions.

At least previously you got 5 minutes of actual time from a casting director, the actual director, etc. So it's actually way more inefficient for you now. Plus, if you're lucky enough to be looked at and they like you, you probably have to go for an in-person audition anyway so what's happened here? You've just added another layer and way more work.

Companies think they're "winning" here by saving labor but I think that's short-sighted. What'll end up happening is AI agents will rise to help people on the other side of that. You can think of using AI to cheat on school assignments as an example of that.

So what will we end up with? AI agents inundating AI systems, which just adds a whole bunch of inefficiency.

[1]: https://www.youtube.com/watch?v=Y1gFSENorEY

WildSense 3 hours ago [-]
[flagged]
pevansgreenwood 9 hours ago [-]
Was it Blaise Pascal who wrote:

I have only made this letter longer because I have not had the time to make it shorter.

The argument that "using AI to generate text is disrespectful because it took no effort to write" misses the point. Respect for the recipient is measured by whether the message serves the recipient's needs, not how it is produced. Similarly, any errors are the senders responsibility, and not the fault of the tools they used.

justanotherjoe 6 minutes ago [-]
what's stopping someone to feed it to an llm and say 'make it simpler' and maybe run it twice.
xp84 9 hours ago [-]
I agree that the bottom line really ought to be usefulness; if it's useful and doesn't waste my time, it's fine if you received it by the use of seer stones for all I care.

However, I don't blame anybody for having red lines like this:

1. Don't send me a big long string that is merely LLM output resulting from pasting a trivial prompt + text I already have access to (or my own words!). I know about Claude too, and if that's what I wanted I'd have done it myself.

2. Don't throw an AI-generated argument at me that you don't even fully understand.

3. If you're preparing information for me, and it's overly verbose and wastes my time, I'll be twice as mad if it's obvious AI than if it's obviously human. This is basically the article's point. The asymmetry of wasting an hour of my time reading a bunch of crap that took 15 seconds of your time should make it clear why this is antisocial behavior.

mapontosevenths 8 hours ago [-]
Exactly. What I want is not effort. It is quality. The sweat of your brow is just gross salt water.

Use whatever tool does the job, and own it if you use the wrong tool and it sucks.

oudlys 9 hours ago [-]
[dead]
ins199 7 hours ago [-]
[flagged]
tomsop 2 hours ago [-]
[dead]
Rekindle8090 9 hours ago [-]
If you use AI to write your communications I don't want to work with you
dataviz1000 9 hours ago [-]
[flagged]
tayo42 9 hours ago [-]
The topic is about person to person communication when collaborating. Advertising isn't relevant at all
sublinear 8 hours ago [-]
Not relevant at all.

You don't need an ad when you already have their attention. The blog post title just sucks. They really mean "don't waste my time with this shit".

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 08:51:37 GMT+0000 (Coordinated Universal Time) with Vercel.