Tap a claim on the ring to put it at the centre.
← As software projects grow more numerous, fast-moving, and…
17 connected korrents · 18 moments from 24 Aug 2009 to 25 Sept 2026.
Everything filed under software quality
software quality
Everything filed under design
design
Everything filed under cybersecurity
cybersecurity
Everything filed under patience
patience
Everything filed under Trauma
Trauma
Everything filed under humility
humility
Everything filed under LLMs
LLMs 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: As software projects grow more numerous, fast-moving, and interdependent, cross-project regressions become practically inevitable. As software projects grow more numerous, fast-moving, and interdependent, cross-project regressions become practically inevitable. Last stated 2 years ago
9 Mar 2025
NE
Nelson Elhage — holds since 2025-03-09 — tap for who they are
Same subject: Finding vulnerabilities in code has become cheaper, but reproducing, fixing, reviewing and backporting the fixes has not. — tap to centre the map on it Finding vulnerabilities in code has become cheaper, but reproducing, fixing, reviewing and backporting the fixes has not. Last stated a month ago
25 Sept 2026
JK
Jean-Baptiste Kempf — holds since 2026-09-25 — 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 2 years ago
1 May 2025
JS
John Siracusa — holds since 2025-05-01 — tap for who they are
Same subject: Software is going through a fast-fashion phase where projects are thrown away if nobody uses them at once; builders should have conviction and work on things longer. — tap to centre the map on it Software is going through a fast-fashion phase where projects are thrown away if nobody uses them at once; builders should have conviction and work on things longer. Last stated 5 months ago
12 Jun 2026
BV
Ben Vinegar — holds since 2026-06-12 — tap for who they are
Same subject: Coming into a project with a guess about what the data will show has, again and again, turned out to be wrong. — tap to centre the map on it Coming into a project with a guess about what the data will show has, again and again, turned out to be wrong. Last stated 6 months ago
8 May 2026
DR
David Reich — holds since 2026-05-08 — tap for who they are
Same subject: Software is not uniquely unpredictable; other engineering disciplines are hit by the same surprises and overruns. — tap to centre the map on it Software is not uniquely unpredictable; other engineering disciplines are hit by the same surprises and overruns. Last stated 6 years ago
20 Jan 2021
HW
Hillel Wayne — holds since 2021-01-20 — tap for who they are
Same subject: A project that only shows the models are not ready yet is a win if it leaves behind an eval to retry with later models. — tap to centre the map on it A project that only shows the models are not ready yet is a win if it leaves behind an eval to retry with later models. Last stated 2 months ago
10 Sept 2026
MK
Mike Krieger — holds since 2026-09-10 — tap for who they are
Same subject: Software becomes more robust when the names used inside its code reflect the intention behind it. — tap to centre the map on it Software becomes more robust when the names used inside its code reflect the intention behind it. Last stated 4 months ago
17 Jul 2026
KR
Kenneth Reitz — holds since 2026-07-17 — tap for who they are
Same subject: Software projects should break downstream users as little as possible, and make any breakage they do cause obvious and easy to fix. — tap to centre the map on it Software projects should break downstream users as little as possible, and make any breakage they do cause obvious and easy to fix. Last stated 5 years ago
11 Dec 2021
DC
David Crawshaw — holds since 2021-12-11 — tap for who they are
Same subject: 95 percent of the software made in an age of abundance will be shitty, and shitty software is easy to deal with because it goes away. — tap to centre the map on it 95 percent of the software made in an age of abundance will be shitty, and shitty software is easy to deal with because it goes away. Last stated a month ago
23 Sept 2026
GT
Geoff Teehan — holds since 2026-09-23 — tap for who they are
Same subject: A bug live for one day is better than an app stuck in review for two weeks. — tap to centre the map on it A bug live for one day is better than an app stuck in review for two weeks. Last stated 17 years ago
24 Aug 2009
JH
Joe Hewitt — holds since 2009-08-24 — 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: 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 9 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 3 months ago
19 Aug 2026
JS
Jon Seager — holds since 2026-08-19 — tap for who they are
Same subject: AI-generated code should not count as finished work until a human has reviewed and corrected it. — tap to centre the map on it AI-generated code should not count as finished work until a human has reviewed and corrected it. Last stated 7 months ago
1 Apr 2026
DJ
Daniel Jalkut — holds since 2026-04-01 — 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 8 months ago
10 Mar 2026
JS
Jon Seager — holds since 2026-03-10 — 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 4 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 5 months ago
7 Jun 2026
TF
Tony Fadell — holds since 2026-06-07 — tap for who they are
At the centre
As software projects grow more numerous, fast-moving, and interdependent, cross-project regressions become practically inevitable.
Holds Read this korrent →
Finding vulnerabilities in code has become cheaper, but reproducing, fixing, reviewing and backporting the fixes has not.
Holds
Software development does not proceed along a straight, predictable path
Holds
Software is going through a fast-fashion phase where projects are thrown away if nobody uses them at once; builders should have conviction and work on things longer.
Holds
Coming into a project with a guess about what the data will show has, again and again, turned out to be wrong.
Holds
Software is not uniquely unpredictable; other engineering disciplines are hit by the same surprises and overruns.
Holds
A project that only shows the models are not ready yet is a win if it leaves behind an eval to retry with later models.
Holds
Software becomes more robust when the names used inside its code reflect the intention behind it.
Holds
Software projects should break downstream users as little as possible, and make any breakage they do cause obvious and easy to fix.
Holds
95 percent of the software made in an age of abundance will be shitty, and shitty software is easy to deal with because it goes away.
Holds
A bug live for one day is better than an app stuck in review for two weeks.
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
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
AI-generated code should not count as finished work until a human has reviewed and corrected it.
Holds
A developer using AI coding tools remains responsible for reviewing the code they ship.
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