Tap a claim on the ring to put it at the centre.
← Agent-written code that runs and passes its tests is not enough:…
17 connected korrents · 14 moments on record from 2 Jun 2024 to 3 Sept 2026.
Everything filed under Anthropic
Anthropic
Everything filed under coding agents
coding agents
Everything filed under Ruby on Rails
Ruby on Rails
Everything filed under MCP
MCP
Everything filed under software quality
software quality
Everything filed under AI agents
AI agents
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: 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.
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: In an agent-written codebase the agent-written tests are equally untrustworthy; manually using the product is the only reliable measure of whether it works. — tap to centre the map on it
In an agent-written codebase the agent-written tests are equally untrustworthy; manually using the product is the only reliable measure of whether it works.
Last stated 5 months ago
25 Mar 2026
MZ
Mario Zechner — holds since 2026-03-25 — 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: 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: Writing code with a coding agent and no tests at all is indefensible, because the old objection to testing — that it is extra work you then have to maintain — no longer applies. — tap to centre the map on it
Writing code with a coding agent and no tests at all is indefensible, because the old objection to testing — that it is extra work you then have to maintain — no longer applies.
Last stated 6 months ago
19 Mar 2026
SW
Simon Willison — holds since 2026-03-19 — tap for who they are
Same subject: A passing test suite is not evidence that the software works, so an agent must also be made to start the thing and exercise it the way a person would. — tap to centre the map on it
A passing test suite is not evidence that the software works, so an agent must also be made to start the thing and exercise it the way a person would.
Last stated 6 months ago
19 Mar 2026
SW
Simon Willison — holds since 2026-03-19 — tap for who they are
Same subject: What limits you with coding agents is your own skill at stringing them together, not the capability of the models. — tap to centre the map on it
What limits you with coding agents is your own skill at stringing them together, not the capability of the models.
Last stated 6 months ago
20 Mar 2026
AK
Andrej Karpathy — holds since 2026-03-20 — tap for who they are
Same subject: A team can stop reading the code it ships, but only by first working out how its agents are to prove that what they wrote actually works. — tap to centre the map on it
A team can stop reading the code it ships, but only by first working out how its agents are to prove that what they wrote actually works.
Last stated 6 months ago
19 Mar 2026
SW
Simon Willison — holds since 2026-03-19 — tap for who they are
Same subject: Rust may be the best language for AI agents to write, because the compiler gives an agent the feedback that tells it what to fix. — tap to centre the map on it
Rust may be the best language for AI agents to write, because the compiler gives an agent the feedback that tells it what to fix.
Last stated 4 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — 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 5 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 6 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
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 on record holding the claim — tap it for who they are faded, dashed ring: they no longer hold it — they changed their mind
At the centre
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 7 Jun 2026 · 3 months ago
Holds TF Tony Fadell
Read this korrent →
Similar wording
In an agent-written codebase the agent-written tests are equally untrustworthy; manually using the product is the only reliable measure of whether it works.
Last stated 25 Mar 2026 · 5 months ago
Holds Mario Zechner
Similar wording
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 19 Jul 2026 · 2 months ago
Holds ES Elizabeth Stone
Similar wording
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 19 Mar 2026 · 6 months ago
Holds Simon Willison
Similar wording
Writing code with a coding agent and no tests at all is indefensible, because the old objection to testing — that it is extra work you then have to maintain — no longer applies.
Last stated 19 Mar 2026 · 6 months ago
Holds Simon Willison
Similar wording
A passing test suite is not evidence that the software works, so an agent must also be made to start the thing and exercise it the way a person would.
Last stated 19 Mar 2026 · 6 months ago
Holds Simon Willison
Similar wording
What limits you with coding agents is your own skill at stringing them together, not the capability of the models.
Last stated 20 Mar 2026 · 6 months ago
Holds Andrej Karpathy
Similar wording
A team can stop reading the code it ships, but only by first working out how its agents are to prove that what they wrote actually works.
Last stated 19 Mar 2026 · 6 months ago
Holds Simon Willison
Similar wording
Rust may be the best language for AI agents to write, because the compiler gives an agent the feedback that tells it what to fix.
Last stated 20 May 2026 · 4 months ago
Holds AR Alice Ryhl
Same subject: Anthropic
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 3 Sept 2026 · 5 days ago
Holds Dax Raad
Same subject: Anthropic
A language model asked to summarize its own system prompt risks that prompt's content biasing the summary it produces.
Last stated 2 Sept 2026 · 6 days ago
Holds Simon Willison
Same subject: Anthropic
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 10 May 2026 · 4 months ago
Holds ER Eric Ries
Same subject: MCP
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 12 Feb 2026 · 7 months ago
Holds Peter Steinberger
Same subject: MCP
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 Jun 2026 · 3 months ago
Holds KH Kelsey Hightower
Same subject: MCP
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 25 Aug 2025 · a year ago
Holds Peter Steinberger
Same subject: Ruby on Rails
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 12 Jul 2025 · a year ago
Holds David Heinemeier Hansson
Same subject: Ruby on Rails
Ruby on Rails took off because its creator evangelized it by arguing its superiority against the competing alternatives.
Last stated 2 Jun 2024 · 2 years ago
No longer holds David Heinemeier Hansson
Same subject: Ruby on Rails
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 12 Jul 2025 · a year ago
No longer holds David Heinemeier Hansson