AI, three at a time · read · watch · listen

Tag

code-review

4 reads

The Register · 2026-10-17 2026-10-23-w1

Postgres 19 delayed after AI reviewers find more bugs than humans can fix

Postgres is the week's cleanest measurement of what cheap detection costs downstream. GA moved to about November 19, 2026 and 8 to 10 significant features went back to PG20, after LLM-assisted review produced about 40 reports averaging a three-line fix. The quality bar rose after the features were written and committed, so finished work became work in doubt. Grant review and PHP's patch race follow the same pattern with different people absorbing the load. Watch PG20, which was expected to be bug-fix-only and now carries the leftovers; a verifier only pays off if remediation capacity grows to match.

The Register 2026-10-17-3

Postgres 19 delayed after AI reviewers find more bugs than humans can fix

Postgres 19 GA slipped from late September or early October to about November 19, 2026, and 8 to 10 features went back to PG20, because LLM-assisted review found more than the beta window could absorb. Eisentraut's example is about 40 reports averaging a three-line fix, each still carrying triage, patch, review, commit and backpatch overhead. PG20 was expected to be bug-fix-only and now inherits the leftovers, so a verifier like VAGEN pays off only if remediation capacity grows to match.

AI Engineer (YouTube) 2026-10-14-2

The Death of the Code Review: What the Data Actually Says — Laurie Voss, Arize AI

Review isn't disappearing; the unit of human review is moving from the diff to the definition of good. Every no-human showcase, from OpenAI's roughly 1M lines and 1,500 merged PRs with three engineers to Bun's 6-day Rust port, had humans authoring the verifier, and the Bun port still carries 13,044 unsafe blocks against about 74 in comparable human code. Whoever codifies mergeability into rubrics and evals sets what agents treat as done.

Anthropic Engineering 2026-10-14-3

Redesigning source control at Anthropic

Anthropic's merge queue stopped working once merged changes went from about 2,500 a day in May to over 30,000 in September, so the gate moved to post-merge testing and agent conflict repair. That swaps a process control for a bet on agent competence, and the post doesn't publish failure data to show the bet is safe. Checkout, CI and merge are the next layers to be rebuilt as server-side services, since 25 million daily CI checkouts can't be fetched like a human would.