Tap a claim on the ring to put it at the centre.
← Lines of code are the wrong artifact to review; what we should be…
17 connected korrents · 15 moments from 29 Jun 2023 to 24 Sept 2026.
Everything filed under software quality
software quality
Everything filed under code generation
code generation
Everything filed under LLMs
LLMs
Everything filed under documentation
documentation
Everything filed under vibe coding
vibe coding
Everything filed under design
design
Everything filed under software performance
software performance
Everything filed under AI slop
AI slop
Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject
Read this korrent: 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.
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.
Last stated 2 months ago
12 Aug 2026
CM
Charity Majors — holds since 2026-08-12 — tap for who they are
Same subject: Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth. — tap to centre the map on it
Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth.
Last stated 3 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
Same subject: 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. — tap to centre the map on it
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.
Last stated 7 months ago
29 Mar 2026
CH
Chip Huyen — holds since 2026-03-29 — tap for who they are
Same subject: 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. — tap to centre the map on it
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.
Last stated 2 months ago
26 Aug 2026
DH
David Heinemeier Hansson — holds since 2026-08-26 — tap for who they are
Same subject: Once you control the ideas behind a piece of software, reviewing the code itself becomes largely unnecessary. — tap to centre the map on it
Once you control the ideas behind a piece of software, reviewing the code itself becomes largely unnecessary.
Last stated 3 months ago
13 Jul 2026
SS
Salvatore Sanfilippo — holds since 2026-07-13 — tap for who they are
Same subject: 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. — tap to centre the map on it
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.
Last stated 3 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
Same subject: In the future, humans will not find bugs in model-produced code in reasonable time and will only review system composition, not via PRs or line-by-line review. — tap to centre the map on it
In the future, humans will not find bugs in model-produced code in reasonable time and will only review system composition, not via PRs or line-by-line review.
Last stated a month ago
19 Sept 2026
TB
Thorsten Ball — holds since 2026-09-19 — tap for who they are
Same subject: 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. — tap to centre the map on it
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.
Last stated 3 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
Same subject: Everyone on a team who makes architectural decisions must understand performance, because a codebase that can be optimized later only ends up that way on purpose. — tap to centre the map on it
Everyone on a team who makes architectural decisions must understand performance, because a codebase that can be optimized later only ends up that way on purpose.
Last stated 2 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: A model can now port essentially any codebase from one programming language to another, work that used to take a team over a year. — tap to centre the map on it
A model can now port essentially any codebase from one programming language to another, work that used to take a team over a year.
Last stated 3 months ago
27 Jul 2026
BC
Boris Cherny — holds since 2026-07-27 — tap for who they are
Same subject: AI acceleration threatens 'less software': without the constraint of scarce hours, even 37signals will likely build too much. — tap to centre the map on it
AI acceleration threatens 'less software': without the constraint of scarce hours, even 37signals will likely build too much.
Last stated 3 months ago
26 Jul 2026
DH
David Heinemeier Hansson — holds since 2026-07-26 — tap for who they are
Same subject: AI code generation's default reward loop works like a slot machine and undermines skill retention. — tap to centre the map on it
AI code generation's default reward loop works like a slot machine and undermines skill retention.
Last stated 5 months ago
28 May 2026
VB
Vicki Boykis — holds since 2026-05-28 — tap for who they are
Same subject: AI coding tools perform better on greenfield projects than on existing codebases, though the advantage is smaller than commonly assumed. — tap to centre the map on it
AI coding tools perform better on greenfield projects than on existing codebases, though the advantage is smaller than commonly assumed.
Last stated 9 months ago
22 Jan 2026
SK
Steve Klabnik — holds since 2026-01-22 — tap for who they are
Same subject: AI coding tools remove the natural filter that slow, effortful building placed on which ideas actually get built. — tap to centre the map on it
AI coding tools remove the natural filter that slow, effortful building placed on which ideas actually get built.
Last stated 4 months ago
17 Jun 2026
ES
Elio Struyf — holds since 2026-06-17 — tap for who they are
Same subject: If Copilot is meaningfully helping you write code, that is evidence your framework or library is bad and full of boilerplate. — tap to centre the map on it
If Copilot is meaningfully helping you write code, that is evidence your framework or library is bad and full of boilerplate.
Last stated 3 years ago
29 Jun 2023
GH
George Hotz — holds since 2023-06-29 — tap for who they are
Same subject: Modern AI models tend to write tests for every tiny change, even when those tests aren't useful. — tap to centre the map on it
Modern AI models tend to write tests for every tiny change, even when those tests aren't useful.
Last stated 4 weeks ago
24 Sept 2026
PS
Peter Steinberger — holds since 2026-09-24 — tap for who they are
Same subject: A badly written AI outbound email is evidence of a bad vendor, not of a limit of AI. — tap to centre the map on it
A badly written AI outbound email is evidence of a bad vendor, not of a limit of AI.
Last stated 10 months ago
1 Jan 2026
JL
Jason Lemkin — holds since 2026-01-01 — tap for who they are
Same subject: A growing fraction of social media is AI slop influencers being replied to by bots — an echo of an echo of an echo. — tap to centre the map on it
A growing fraction of social media is AI slop influencers being replied to by bots — an echo of an echo of an echo.
Last stated 2 months ago
23 Aug 2026
FC
François Chollet — holds since 2026-08-23 — tap for who they are
same subject or similar wording a cloud: claims about one subject, named for it bar: when it was last stated, on a scale from 2015 to today — full is today a face: someone who holds the claim — tap it for who they are
At the centre
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.
Last stated 12 Aug 2026 · 2 months ago
Holds Charity Majors
Read this korrent →
Similar wording
Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth.
Last stated 15 Jul 2026 · 3 months ago
Holds Dex Horthy
Similar 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.
Last stated 29 Mar 2026 · 7 months ago
Holds Chip Huyen
Similar 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.
Last stated 26 Aug 2026 · 2 months ago
Holds David Heinemeier Hansson
Similar wording
Once you control the ideas behind a piece of software, reviewing the code itself becomes largely unnecessary.
Last stated 13 Jul 2026 · 3 months ago
Holds Salvatore Sanfilippo
Similar 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.
Last stated 15 Jul 2026 · 3 months ago
Holds Dex Horthy
Similar wording
In the future, humans will not find bugs in model-produced code in reasonable time and will only review system composition, not via PRs or line-by-line review.
Last stated 19 Sept 2026 · a month ago
Holds Thorsten Ball
Similar 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.
Last stated 15 Jul 2026 · 3 months ago
Holds Dex Horthy
Similar wording
Everyone on a team who makes architectural decisions must understand performance, because a codebase that can be optimized later only ends up that way on purpose.
Last stated 26 Aug 2026 · 2 months ago
Holds Casey Muratori
Same subject: code generation
A model can now port essentially any codebase from one programming language to another, work that used to take a team over a year.
Last stated 27 Jul 2026 · 3 months ago
Holds Boris Cherny
Same subject: code generation
AI acceleration threatens 'less software': without the constraint of scarce hours, even 37signals will likely build too much.
Last stated 26 Jul 2026 · 3 months ago
Holds David Heinemeier Hansson
Same subject: code generation
AI code generation's default reward loop works like a slot machine and undermines skill retention.
Last stated 28 May 2026 · 5 months ago
Holds Vicki Boykis
Same subject: developer tools
AI coding tools perform better on greenfield projects than on existing codebases, though the advantage is smaller than commonly assumed.
Last stated 22 Jan 2026 · 9 months ago
Holds Steve Klabnik
Same subject: developer tools
AI coding tools remove the natural filter that slow, effortful building placed on which ideas actually get built.
Last stated 17 Jun 2026 · 4 months ago
Holds Elio Struyf
Same subject: developer tools
If Copilot is meaningfully helping you write code, that is evidence your framework or library is bad and full of boilerplate.
Last stated 29 Jun 2023 · 3 years ago
Holds George Hotz
Same subject: AI slop
Modern AI models tend to write tests for every tiny change, even when those tests aren't useful.
Last stated 24 Sept 2026 · 4 weeks ago
Holds Peter Steinberger
Same subject: AI slop
A badly written AI outbound email is evidence of a bad vendor, not of a limit of AI.
Last stated 1 Jan 2026 · 10 months ago
Holds Jason Lemkin
Same subject: AI slop
A growing fraction of social media is AI slop influencers being replied to by bots — an echo of an echo of an echo.
Last stated 23 Aug 2026 · 2 months ago
Holds François Chollet