[hoherd]

Seriously this. Doing code reviews on LLM created code is so frustrating. If the code was submitted by a junior engineer I could get on zoom with them and educate them, which would make them a better team mate, advance their career goals, and make the world slightly better. With AI created code the review process is a series of tiny struggles to dig up out of the hole the LLM created and get back to baseline code quality, and it'll probably be the same Sisyphean struggle with the next PR.

[soraminazuki]

I had to review code that couldn't even do a straightforward map, filter, and reduce properly. But with management pushing hard for AI use, I feel powerless to push back against it.

[antisol]

Ha! Not just "the next PR", in my experience about 30% of the time you tell it "hey this slop you gave me is horribly broken because <reason>", and it says "you're absolutely right! I totally 100% understand the problem now, and I'll totally 100% fix that for you right now!", and then proceeds to deliver exactly the same broken slop it game me before.

[jimbokun]

Interesting, isn’t it?

It knows that the apologetic tone and acknowledging understanding of your critique is the most probable response for it to generate. But that’s very different from actually understanding how it should change the code.

[ath3nd]

There is a reason why maintainers of OSS tools reject AI slop PRs: https://www.theregister.com/2025/07/15/curl_creator_mulls_ni...