Rust's Clippy has adopted a more nuanced review-PRs-to-get-yours-reviewed system [2], this impressed me and made me think of whether there are other perhaps similarly "gamified" ways to handle the LLM storm.

There is also Vouch, as previously discussed on HN. [3]

[1] https://ladybird.org/posts/changing-how-we-develop-ladybird/

[2] https://blog.rust-lang.org/inside-rust/2026/07/06/unite-for-clippy/

[3] https://news.ycombinator.com/item?id=46930961

Do you have ideas or seen other projects handle this differently? What is the situation like for your project?

Comments URL: https://news.ycombinator.com/item?id=48949019

Points: 2

# Comments: 0

I think Linus' position even pre-LLM-coding – basically not trusting any code he gets, and not writing any code himself, just reviewing a ton of it – is strikingly similar to how most people now do "software engineering" (or vibe coding/agentic engineering or whatever you want to call what we're doing nowadays).

From his perspective, the only things that changed is that he can more quickly/better review code and find bugs, and maintainers below him are somewhat more annoyed due to the influx of AI slop.

[1] https://news.ycombinator.com/item?id=48897104

On an unrelated note: yes, I also don't understand how this incident has to do much with social media bans…

> Just because there are adults with full agency that do the wrong thing, doesn't mean we should remove protections on young people. Just because adults with full agency drive recklessly, doesn't mean we should allow 13 year olds the ability to drive.

also agree wholeheartedly.