Tap a claim on the ring to put it at the centre.
← Sandboxing is the single most important protection for a coding agent,…
17 connected korrents · 12 moments on record from 2 Jun 2024 to 3 Sept 2026.
Everything filed under coding agents
coding agents
Everything filed under Anthropic
Anthropic
Everything filed under Ruby on Rails
Ruby on Rails
Everything filed under MCP
MCP
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: Sandboxing is the single most important protection for a coding agent, because it is the only one that bounds the damage when the agent is successfully tricked. Sandboxing is the single most important protection for a coding agent, because it is the only one that bounds the damage when the agent is successfully tricked. Last stated 6 months ago
19 Mar 2026
SW
Simon Willison — holds since 2026-03-19 — tap for who they are
Same subject: Working with coding agents is a skill you learn like an instrument; judging the tools after one try is like calling a piano bad after one go. — tap to centre the map on it Working with coding agents is a skill you learn like an instrument; judging the tools after one try is like calling a piano bad after one go. Last stated 7 months ago
12 Feb 2026
PS
Peter Steinberger — holds since 2026-02-12 — 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: Test-driven development matters more with coding agents than it ever did with people, because its real effect is stopping the agent writing more code than the task needs. — tap to centre the map on it Test-driven development matters more with coding agents than it ever did with people, because its real effect is stopping the agent writing more code than the task needs. 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: 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 language-agnostic conformance suite is the most powerful thing you can hand a coding agent, because the whole instruction becomes: write code until these tests pass. — tap to centre the map on it A language-agnostic conformance suite is the most powerful thing you can hand a coding agent, because the whole instruction becomes: write code until these tests pass. 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: Working with a coding agent should leave both of you better every day, and that only happens if you deliberately record what was learned and decided in the session. — tap to centre the map on it Working with a coding agent should leave both of you better every day, and that only happens if you deliberately record what was learned and decided in the session. Last stated 3 weeks ago
19 Aug 2026
AO
Addy Osmani — holds since 2026-08-19 — 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
Sandboxing is the single most important protection for a coding agent, because it is the only one that bounds the damage when the agent is successfully tricked.
Holds Read this korrent →
Working with coding agents is a skill you learn like an instrument; judging the tools after one try is like calling a piano bad after one go.
Holds
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
Test-driven development matters more with coding agents than it ever did with people, because its real effect is stopping the agent writing more code than the task needs.
Holds
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.
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 language-agnostic conformance suite is the most powerful thing you can hand a coding agent, because the whole instruction becomes: write code until these tests pass.
Holds
What limits you with coding agents is your own skill at stringing them together, not the capability of the models.
Holds
Working with a coding agent should leave both of you better every day, and that only happens if you deliberately record what was learned and decided in the session.
Holds AO Addy Osmani
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