Engineers argue over refusing AI while review agents reach 72% bug detection

Rich Hickey’s LinkedIn essay “‘AI’ Is Not a Tool” reached 137 points and 65 comments on Hacker News in the last day, and a rebuttal titled “AI Is a Tool. Using It Well Takes Skill.” drew 120 points and 102 comments on the same front page. They led a cluster of threads about whether engineers should accept these systems in their work at all. Micah Lee’s “Just say no to OpenAI and Anthropic” collected 125 points, a post titled “Fable Took My Job” sat beside it with 144 points and 165 comments, and The Atlantic ran a piece called “The Tragedy of AI Coding.” The feed carries headlines and scores for most of these and no full text, so the positions are best read at the source. The one available in full is Sean Goedecke’s reply to the refusers, which argues that software engineers “are the last people in the world who should be complaining about this” because the trade has always been about automating other people’s work, from typing pools to travel agencies. Engineers who admire the Luddites have the casting wrong, he writes: programmers are “the smiths and mechanics who built the power looms in the first place,” and those mechanics were themselves automated away fifty years later.

The highest-scoring thread in the cluster concerned policy. A pull request against the QGIS enhancement-proposals repository reached 179 points and 137 comments under the headline “QGIS bans AI assisted contributions.” A pull request in a proposals repository can still be under discussion, so check its scope and merge status before citing it as settled. If it stands, one of the larger open-source GIS projects will have turned the essay argument into contribution rules, and other maintainers will have text to copy or reject.

Spotify put numbers on what adoption costs after the code is written. InfoQ reports that AI-assisted development more than doubled the company’s monthly merged changes, and that the volume prompted a review of quality and reliability controls across engineering, with changes to testing, observability, rollback capacity, workload prioritization and automated maintenance. Doubling the merge rate became a reliability program, which is the review bottleneck from yesterday’s issue seen from the operations side.

Two papers in Monday’s arXiv cs.SE batch measure how much of that checking agents can take on. CRBugBench, from a team that includes Christian Bird and Emerson Murphy-Hill, pairs human-verified bugs with the pull requests that introduced them: 1,000 review tasks across 98 open-source repositories, plus 800 from proprietary repositories at one large company. The best configuration, claude-opus-5 with copilot-cli, catches 71.9% of bugs within its top five comments, up from 47.7% for opus-4.6 five months earlier. Detection drops sharply on the proprietary repositories, where project context matters more, and on bugs that need non-local reasoning, so the open-source figure is the optimistic one for most teams. TestSuiteBench hands agents detailed specifications for 165 open-source applications and asks for a test suite from scratch. Frontier agents score below 60% on mutation testing even though 88% of their tests pass on the reference implementation, while implementations generated from the same specifications pass 82% of the reference tests. The authors’ one-line version is that agents “can build software they cannot verify.”

Anthropic’s answer to the bottleneck is more agents. At AI Engineer New York on Monday, CJ Avilla and Harrison Stall walked through dynamic workflows, the Managed Agents feature announced Friday in which Claude writes its own orchestration program instead of running a developer-configured coordinator and roster. Latent Space’s writeup is most useful for the audience questions. The lead agent does not know its budget while running, though developers can set a session budget. Subagents share a filesystem but cannot be told through the API to message each other. On the workshop’s stock-watchlist example, Avilla said flows cost “much more” than a single agent and were “much more effective at finding all of the details.” AlphaSignal led its Monday issue with the number in circulation, 66 of 70 bugs found in a 116,000-line codebase by a 1,000-agent run against roughly 27 for one agent. Stall’s own description is the accurate one: “a way to throw test-time compute at hard problems.”

Two toolchain items are worth ten minutes this morning. The highest-scoring AI thread of the day, at 191 points and 115 comments, was an issue on openai/codex titled “Codex CLI installs a persistent, self-updating background daemon by default.” Separately, a commit in the Zod repository reached 124 points under the headline “Zod 4.6.6 compromised by malware?” The question mark is part of the headline and the feed holds no confirmed advisory, so treat it as a reason to check which version your lockfile resolves, and read the Codex issue against what the CLI has registered to run on your machine.

Outside developer tools, Bloomberg reported that Epic Games delayed a Disney project and asked its developers to use more AI; AV Club and r/vibecoding picked the story up in the last day. A slipped schedule answered with an AI mandate will be claimed as evidence by both camps in the Hickey argument.

What to watch: whether the QGIS proposal merges and whether other projects adopt its language. Artificial Analysis published FrontierCode, which asks whether AI models can write code maintainers would merge, the measurement that argument lacks. Anthropic posted research notes on whether models may be capable of self-replicating without access to a datacenter and on defenses against distillation attacks, and the OpenAI math story picked up an 82-point look at the claimed faster Fourier transform result on the argmin blog. The question under all of it is the one TestSuiteBench poses: if agents build more than they can verify, what closes the gap at Spotify’s merge rate?

Feed note: the mirror status row reports its last sync as 2026-09-01, but items in the feed run through the morning of 2026-10-13. Treated as a stale status row, not a stale feed.