Tap a claim on the ring to put it at the centre.
← Software bugs most often arise at boundaries where reality does not…
17 connected korrents · 17 moments from 18 Jan 2021 to 21 Sept 2026.
Everything filed under software quality
software quality
Everything filed under open source
open source
Everything filed under documentation
documentation 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: Software bugs most often arise at boundaries where reality does not respect the divisions assumed by the source code. Software bugs most often arise at boundaries where reality does not respect the divisions assumed by the source code. Last stated 3 months ago
17 Jul 2026
KR
Kenneth Reitz — holds since 2026-07-17 — tap for who they are
Same subject: Software engineers behave as though the world exists in the repository, and it does not: the world is production. — tap to centre the map on it Software engineers behave as though the world exists in the repository, and it does not: the world is production. Last stated 2 months ago
12 Aug 2026
CM
Charity Majors — holds since 2026-08-12 — tap for who they are
Same subject: Software development does not proceed along a straight, predictable path — tap to centre the map on it Software development does not proceed along a straight, predictable path Last stated a year ago
1 May 2025
JS
John Siracusa — holds since 2025-05-01 — tap for who they are
Same subject: A person does not truly control a piece of software if they do not control its source code. — tap to centre the map on it A person does not truly control a piece of software if they do not control its source code. Last stated 2 months ago
31 Jul 2026
AK
Andrew Kelley — holds since 2026-07-31 — tap for who they are
Same subject: The specific rules taught as clean code are simply bad programming practices, and they get worse when you apply them together. — tap to centre the map on it The specific rules taught as clean code are simply bad programming practices, and they get worse when you apply them together. Last stated a month ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: Publishing the source is not the same as developing in the open, and only the second changes how the work actually goes. — tap to centre the map on it Publishing the source is not the same as developing in the open, and only the second changes how the work actually goes. Last stated 5 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: Veterans of the 1990s free software movement do not understand the world today’s maintainers work in, and should listen before proposing fixes for it. — tap to centre the map on it Veterans of the 1990s free software movement do not understand the world today’s maintainers work in, and should listen before proposing fixes for it. Last stated 3 years ago
1 Apr 2024
TD
Thomas Depierre — holds since 2024-04-01 — tap for who they are
Same subject: Software development is separated from engineering by circumstance rather than essence, and most programmers could cross that gap without retraining. — tap to centre the map on it Software development is separated from engineering by circumstance rather than essence, and most programmers could cross that gap without retraining. Last stated 6 years ago
18 Jan 2021
HW
Hillel Wayne — holds since 2021-01-18 — tap for who they are
Same subject: Code is not a sufficient source of truth for managing understanding. — tap to centre the map on it Code is not a sufficient source of truth for managing understanding. Last stated 2 weeks ago
21 Sept 2026
FC
François Chollet — holds since 2026-09-21 — tap for who they are
Same subject: A coding agent left to run over a weekend returns work that is half good, a quarter garbage and a quarter in need of repair. — tap to centre the map on it A coding agent left to run over a weekend returns work that is half good, a quarter garbage and a quarter in need of repair. Last stated a year ago
18 Aug 2025
CB
Clay Bavor — holds since 2025-08-18 — tap for who they are
Same subject: A developer using AI coding tools remains responsible for reviewing the code they ship. — tap to centre the map on it A developer using AI coding tools remains responsible for reviewing the code they ship. Last stated 7 months ago
10 Mar 2026
JS
Jon Seager — holds since 2026-03-10 — tap for who they are
Same subject: A feature shipped in a product's official release is fair to judge, regardless of whether the company labels it a beta. — tap to centre the map on it A feature shipped in a product's official release is fair to judge, regardless of whether the company labels it a beta. Last stated 3 weeks ago
14 Sept 2026
JS
Jason Snell — holds since 2026-09-14 — tap for who they are
Same subject: AI-assisted coding will generate a lot of low-quality output that developers will need to clean up, even as it also produces good results. — tap to centre the map on it AI-assisted coding will generate a lot of low-quality output that developers will need to clean up, even as it also produces good results. Last stated 8 months ago
9 Feb 2026
SH
Scott Hanselman — holds since 2026-02-09 — tap for who they are
Same subject: AI-generated code should be treated as untrusted until there is evidence it preserves the intended behavior. — tap to centre the map on it AI-generated code should be treated as untrusted until there is evidence it preserves the intended behavior. Last stated a month ago
19 Aug 2026
JS
Jon Seager — holds since 2026-08-19 — tap for who they are
Same subject: Code review as a review mechanism depends on reviewers being able to infer effort from reading code, and AI-agent-generated code erases that signal. — tap to centre the map on it Code review as a review mechanism depends on reviewers being able to infer effort from reading code, and AI-agent-generated code erases that signal. Last stated 5 months ago
7 May 2026
DC
David Crawshaw — holds since 2026-05-07 — tap for who they are
Same subject: A team that slows down and reads every pull request and every line of code should expect only a 30 to 50 percent productivity lift from AI. — tap to centre the map on it A team that slows down and reads every pull request and every line of code should expect only a 30 to 50 percent productivity lift from AI. Last stated 3 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — 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 4 months ago
7 Jun 2026
TF
Tony Fadell — holds since 2026-06-07 — 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
At the centre
Software bugs most often arise at boundaries where reality does not respect the divisions assumed by the source code.
Holds Read this korrent →
Software engineers behave as though the world exists in the repository, and it does not: the world is production.
Holds
Software development does not proceed along a straight, predictable path
Holds
A person does not truly control a piece of software if they do not control its source code.
Holds
The specific rules taught as clean code are simply bad programming practices, and they get worse when you apply them together.
Holds
Publishing the source is not the same as developing in the open, and only the second changes how the work actually goes.
Holds
Veterans of the 1990s free software movement do not understand the world today’s maintainers work in, and should listen before proposing fixes for it.
Holds
Software development is separated from engineering by circumstance rather than essence, and most programmers could cross that gap without retraining.
Holds
Code is not a sufficient source of truth for managing understanding.
Holds
A coding agent left to run over a weekend returns work that is half good, a quarter garbage and a quarter in need of repair.
Holds
A developer using AI coding tools remains responsible for reviewing the code they ship.
Holds
A feature shipped in a product's official release is fair to judge, regardless of whether the company labels it a beta.
Holds
AI-assisted coding will generate a lot of low-quality output that developers will need to clean up, even as it also produces good results.
Holds
AI-generated code should be treated as untrusted until there is evidence it preserves the intended behavior.
Holds
Code review as a review mechanism depends on reviewers being able to infer effort from reading code, and AI-agent-generated code erases that signal.
Holds
A team that slows down and reads every pull request and every line of code should expect only a 30 to 50 percent productivity lift from AI.
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
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