Lines of code are the wrong artifact to review; what we should be storing and reviewing is an architecture that generates the code to spec.

Added to korrents 12 Aug 2026 · How quotes work · Something wrong? Tell us

Related korrents

Our reading — they may agree, disagree or merely touch the same thing. Closest first: a shared subject counts for most, then how near the wording is.

• Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth. DHDex Horthy15 Jul 2026similar wording
• Line-by-line code review has become an outdated ritual: senior engineers should be giving feedback on how their team instructs AI, not on the code AI wrote. CHChip Huyen29 Mar 2026similar wording
• Work produced by one frontier model should be reviewed by a different one, for the same reason a good programmer's work improves under a good peer's review. DHDavid Heinemeier Hansson26 Aug 2026similar wording
• Agentic code review raises the floor but cannot be trusted, because the model reading the code is the same model that wrote it, and it will tell you the code is great. DHDex Horthy15 Jul 2026similar wording
• Loops belong on codebase quality, not on shipping the features users want; we read all of the code, because program design is what decides whether a codebase stays changeable. DHDex Horthy15 Jul 2026similar wording

See this on the map →