Tap a claim on the ring to put it at the centre.
← Reviewing agent-written code is risk management rather than reading:…
17 connected korrents · 16 moments on record from 2 Jun 2024 to 3 Sept 2026.
Everything filed under Anthropic
Anthropic
Everything filed under Ruby on Rails
Ruby on Rails
Everything filed under MCP
MCP
Everything filed under coding agents
coding agents
Everything filed under software quality
software quality 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: Reviewing agent-written code is risk management rather than reading: how long the change took and how big it is tell you when to look closely. Reviewing agent-written code is risk management rather than reading: how long the change took and how big it is tell you when to look closely. Last stated 4 weeks ago
10 Aug 2026
PS
Peter Steinberger — holds since 2026-08-10 — tap for who they are
Same subject: A plan that spells out every line of code to change gives you no leverage: it costs as long to read as the pull request, so you end up skimming it and reading the code twice. — tap to centre the map on it A plan that spells out every line of code to change gives you no leverage: it costs as long to read as the pull request, so you end up skimming it and reading the code twice. Last stated 2 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
Same subject: Whether agent-written code needs to be good depends entirely on how long it will live: a throwaway single-page tool can be spaghetti, anything maintained cannot. — tap to centre the map on it Whether agent-written code needs to be good depends entirely on how long it will live: a throwaway single-page tool can be spaghetti, anything maintained cannot. Last stated 6 months ago
19 Mar 2026
SW
Simon Willison — holds since 2026-03-19 — tap for who they are
Same subject: The code today’s models and agents write is very hard to follow: you get better performance without knowing why, and no way to fix it when it breaks. — tap to centre the map on it The code today’s models and agents write is very hard to follow: you get better performance without knowing why, and no way to fix it when it breaks. Last stated 2 months ago
19 Jul 2026
ES
Elizabeth Stone — holds since 2026-07-19 — 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 2 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
Same subject: Coding agents made implementation cheap without making roadmaps shorter or software better -- the binding constraint was never how fast code gets written. — tap to centre the map on it Coding agents made implementation cheap without making roadmaps shorter or software better -- the binding constraint was never how fast code gets written. Last stated 3 weeks ago
14 Aug 2026
SP
Sunil Pai — holds since 2026-08-14 — tap for who they are
Same subject: The way software gets built flipped in December: writing code yourself is now the exception, not the default. — tap to centre the map on it The way software gets built flipped in December: writing code yourself is now the exception, not the default. Last stated 6 months ago
20 Mar 2026
AK
Andrej Karpathy — holds since 2026-03-20 — tap for who they are
Same subject: A maintainer no longer needs to read every pull request; agents can sort the chaff and leave only the decisions worth a human. — tap to centre the map on it A maintainer no longer needs to read every pull request; agents can sort the chaff and leave only the decisions worth a human. Last stated 2 weeks ago
26 Aug 2026
DH
David Heinemeier Hansson — holds since 2026-08-26 — tap for who they are
Same subject: Agent-written code that runs and passes its tests is not enough: security, maintainability and being able to roll it back still need humans in the loop. — tap to centre the map on it Agent-written code that runs and passes its tests is not enough: security, maintainability and being able to roll it back still need humans in the loop. Last stated 3 months ago
7 Jun 2026
TF
Tony Fadell — holds since 2026-06-07 — tap for who they are
Same subject: A benchmark that ranks Claude Code last while it stays first in use is measuring the wrong thing, and has been for a year. — tap to centre the map on it A benchmark that ranks Claude Code last while it stays first in use is measuring the wrong thing, and has been for a year. Last stated 4 days ago
3 Sept 2026
DR
Dax Raad — holds since 2026-09-03 — tap for who they are
Same subject: A language model asked to summarize its own system prompt risks that prompt's content biasing the summary it produces. — tap to centre the map on it A language model asked to summarize its own system prompt risks that prompt's content biasing the summary it produces. Last stated 5 days ago
2 Sept 2026
SW
Simon Willison — holds since 2026-09-02 — tap for who they are
Same subject: A trust that owns the mission protects a company better than founder control does, which is why Anthropic needs no dual-class shares. — tap to centre the map on it A trust that owns the mission protects a company better than founder control does, which is why Anthropic needs no dual-class shares. Last stated 4 months ago
10 May 2026
ER
Eric Ries — holds since 2026-05-10 — tap for who they are
Same subject: Every tool is better as a CLI than as an MCP server: models are good at Unix commands, a CLI composes with jq, and MCP output clutters the context. — tap to centre the map on it Every tool is better as a CLI than as an MCP server: models are good at Unix commands, a CLI composes with jq, and MCP output clutters the context. Last stated 7 months ago
12 Feb 2026
PS
Peter Steinberger — holds since 2026-02-12 — tap for who they are
Same subject: MCP is not a new foundation for anything — it is API design, and Kubernetes was already turning one intention into seven calls a decade ago. — tap to centre the map on it MCP is not a new foundation for anything — it is API design, and Kubernetes was already turning one intention into seven calls a decade ago. Last stated 3 months ago
3 Jun 2026
KH
Kelsey Hightower — holds since 2026-06-03 — tap for who they are
Same subject: MCP servers are worth removing outright: an agent reading the code directly is faster, and pollutes its context less, than one that can reach for a tool unasked. — tap to centre the map on it MCP servers are worth removing outright: an agent reading the code directly is faster, and pollutes its context less, than one that can reach for a tool unasked. Last stated a year ago
25 Aug 2025
PS
Peter Steinberger — holds since 2025-08-25 — tap for who they are
Same subject: Calling static typing the only way to build reliable systems is idiotic in the face of the evidence, starting with Shopify serving a million requests a second on Rails. — tap to centre the map on it Calling static typing the only way to build reliable systems is idiotic in the face of the evidence, starting with Shopify serving a million requests a second on Rails. Last stated a year ago
12 Jul 2025
DH
David Heinemeier Hansson — holds since 2025-07-12 — tap for who they are
Same subject: Ruby on Rails took off because its creator evangelized it by arguing its superiority against the competing alternatives. — tap to centre the map on it Ruby on Rails took off because its creator evangelized it by arguing its superiority against the competing alternatives. Last stated 2 years ago
2 Jun 2024
DH
David Heinemeier Hansson — no longer holds since 2024-06-02 — tap for who they are
Same subject: The Rails doctrine's 'progress over stability' is the one point that dated: churn is not progress, and stability turned out to be worth more. — tap to centre the map on it The Rails doctrine's 'progress over stability' is the one point that dated: churn is not progress, and stability turned out to be worth more. Last stated a year ago
12 Jul 2025
DH
David Heinemeier Hansson — no longer holds since 2025-07-12 — tap for who they are
At the centre
Reviewing agent-written code is risk management rather than reading: how long the change took and how big it is tell you when to look closely.
Holds Read this korrent →
A plan that spells out every line of code to change gives you no leverage: it costs as long to read as the pull request, so you end up skimming it and reading the code twice.
Holds DH Dex Horthy
Whether agent-written code needs to be good depends entirely on how long it will live: a throwaway single-page tool can be spaghetti, anything maintained cannot.
Holds
The code today’s models and agents write is very hard to follow: you get better performance without knowing why, and no way to fix it when it breaks.
Holds ES Elizabeth Stone
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.
Holds DH Dex Horthy
Coding agents made implementation cheap without making roadmaps shorter or software better -- the binding constraint was never how fast code gets written.
Holds
The way software gets built flipped in December: writing code yourself is now the exception, not the default.
Holds
A maintainer no longer needs to read every pull request; agents can sort the chaff and leave only the decisions worth a human.
Holds
Agent-written code that runs and passes its tests is not enough: security, maintainability and being able to roll it back still need humans in the loop.
Holds TF Tony Fadell
A benchmark that ranks Claude Code last while it stays first in use is measuring the wrong thing, and has been for a year.
Holds
A language model asked to summarize its own system prompt risks that prompt's content biasing the summary it produces.
Holds
A trust that owns the mission protects a company better than founder control does, which is why Anthropic needs no dual-class shares.
Holds ER Eric Ries
Every tool is better as a CLI than as an MCP server: models are good at Unix commands, a CLI composes with jq, and MCP output clutters the context.
Holds
MCP is not a new foundation for anything — it is API design, and Kubernetes was already turning one intention into seven calls a decade ago.
Holds KH Kelsey Hightower
MCP servers are worth removing outright: an agent reading the code directly is faster, and pollutes its context less, than one that can reach for a tool unasked.
Holds
Calling static typing the only way to build reliable systems is idiotic in the face of the evidence, starting with Shopify serving a million requests a second on Rails.
Holds
Ruby on Rails took off because its creator evangelized it by arguing its superiority against the competing alternatives.
No longer holds
The Rails doctrine's 'progress over stability' is the one point that dated: churn is not progress, and stability turned out to be worth more.
No longer holds