Fix Your AI Slop Problem by Giving Reviewers Credit

Dan Apushkinsky· Oct 5, 2026 · 1:06 AM UTC ·5 min read · 0 reactions · 0 comments · 15 views

More from Hacker News (AI / LLM) ai Compare coverage Trending Talk Blindspots Daily Sources Live wire

#software development #ai #code review #productivity #engineering culture

TL;DR · WeSearch summary

The article argues that relying on multiple AI passes for code review often misses obvious bugs that a human could easily catch by reading the code. It suggests that the current workflow, where human reviewers merely paste code into AI tools, creates a 'no man's land' that fails to leverage human insight effectively. The author proposes adding code reviews as visible subtasks on sprint boards to ensure reviewers receive proper credit for their time and effort.

Key facts

▪An AI-generated code change missed a simple bug related to a missing printer in a specific branch, which was only caught by a human reviewer who actually read the code.
▪The author contends that having multiple AI models review the same code with similar prompts is inefficient and does not replace the value of a human reviewer.
▪Current workflows often leave human reviewers feeling like they are doing invisible, uncredited labor because they spend more time reviewing AI-generated code than the author spent creating it.
▪The proposed solution is to track code reviews as explicit subtasks on sprint boards to make the work visible and ensure reviewers are recognized for their contributions.

About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 7,595 of its stories.

All Hacker News (AI / LLM) coverage →

Original article

Hacker News (AI / LLM) · Dan Apushkinsky

Read full at Hacker News (AI / LLM) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	Hacker News (AI / LLM)
Canonical URL	https://danunparsed.com/p/giving-code-reviewers-credit
Publication time	Mon, 05 Oct 2026 01:06:07 +0000
Retrieval time	2026-10-05T01:12:15.015Z
Last seen	2026-10-05T01:12:15.015Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	3391GLIBoRdl · 1 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

Fix Your AI Slop Problem By Giving Reviewers CreditThree AI passes missed a bug you could find by scrolling upDan ApushkinskyOct 02, 202621ShareApprovedI was reviewing a PR recently. See if you can spot the bug:# Branch C doesn't have a printer user = new Person(...) ... user does some shit ... if user not in branch_c: user.print_document() ... 50 lines of library logic ... ### New code added in the PR: + staff = new Person(...) ... staff does some shit ... + staff.print_document()Obviously I don’t work at a library — I swapped out the real calls. But it was truly that simple. The # Branch C doesn’t have a printer isn’t added here for context either, it’s there, in the code.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (AI / LLM).

Anonymous · no account needed

Discussion

0 comments