Tap a claim on the ring to put it at the centre.
← Repeated rewrites are the correct answer under fast growth, because a…
17 connected korrents · 15 moments from 17 Apr 2025 to 12 Oct 2026.
Everything filed under software quality
software quality
Everything filed under startups
startups
Everything filed under design
design
Everything filed under semiconductors
semiconductors
Everything filed under innovation
innovation
Everything filed under JavaScript
JavaScript
Everything filed under energy
energy 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: Repeated rewrites are the correct answer under fast growth, because a system specified to scale forever would take so long to build that the company would die before it shipped. Repeated rewrites are the correct answer under fast growth, because a system specified to scale forever would take so long to build that the company would die before it shipped. Last stated 7 months ago
1 Apr 2026
TP
Thuan Pham — holds since 2026-04-01 — tap for who they are
Same subject: The right way to specify a rescue rewrite is a couple of scaling constraints and no new features at all, so that hardware can absorb the growth the team has no time to design for. — tap to centre the map on it The right way to specify a rescue rewrite is a couple of scaling constraints and no new features at all, so that hardware can absorb the growth the team has no time to design for. Last stated 7 months ago
1 Apr 2026
TP
Thuan Pham — holds since 2026-04-01 — tap for who they are
Same subject: A computer company has to live five to ten years in the future, because a system takes three years to build, two to ramp, and is then used for a decade. — tap to centre the map on it A computer company has to live five to ten years in the future, because a system takes three years to build, two to ramp, and is then used for a decade. Last stated 3 months ago
26 Jul 2026
JH
Jensen Huang — holds since 2026-07-26 — tap for who they are
Same subject: The fastest-growing companies are not using data well, because they reached enormous scale before they had time to build any of the instrumentation. — tap to centre the map on it The fastest-growing companies are not using data well, because they reached enormous scale before they had time to build any of the instrumentation. Last stated a year ago
21 Sept 2025
JZ
Julie Zhuo — holds since 2025-09-21 — tap for who they are
Same subject: Deploying a new technology at scale takes decades, far longer than the people building it imagine. — tap to centre the map on it Deploying a new technology at scale takes decades, far longer than the people building it imagine. Last stated 2 years ago
17 Apr 2025
RB
Rodney Brooks — holds since 2025-04-17 — tap for who they are
Same subject: Even a long-horizon deep tech company should chase revenue sooner than it thinks, so that it is valued on its roadmap rather than on its probability of dying. — tap to centre the map on it Even a long-horizon deep tech company should chase revenue sooner than it thinks, so that it is valued on its roadmap rather than on its probability of dying. Last stated 2 months ago
7 Aug 2026
MH
Max Hodak — holds since 2026-08-07 — tap for who they are
Same subject: Uber's thousands of microservices were not an architectural preference but a survival decision: under that growth only independent, unblocked teams could build fast enough to stay alive. — tap to centre the map on it Uber's thousands of microservices were not an architectural preference but a survival decision: under that growth only independent, unblocked teams could build fast enough to stay alive. Last stated 7 months ago
1 Apr 2026
TP
Thuan Pham — holds since 2026-04-01 — tap for who they are
Same subject: Most software rewrites fail and take longer than people expect them to. — tap to centre the map on it Most software rewrites fail and take longer than people expect them to. Last stated 2 years ago
19 Apr 2025
BK
Ben Kuhn — holds since 2025-04-19 — tap for who they are
Same subject: Original thoughts do not scale. — tap to centre the map on it Original thoughts do not scale. Last stated a week ago
12 Oct 2026
SP
Sunil Pai — holds since 2026-10-12 — 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 4 weeks ago
23 Sept 2026
GT
Geoff Teehan — holds since 2026-09-23 — 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: 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 2 months ago
19 Aug 2026
JS
Jon Seager — holds since 2026-08-19 — tap for who they are
Same subject: As AI makes it easier to generate code, teams must delete code more aggressively or be overwhelmed by accumulated complexity. — tap to centre the map on it As AI makes it easier to generate code, teams must delete code more aggressively or be overwhelmed by accumulated complexity. Last stated 2 months ago
1 Sept 2026
VB
Vicki Boykis — holds since 2026-09-01 — 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 5 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
Repeated rewrites are the correct answer under fast growth, because a system specified to scale forever would take so long to build that the company would die before it shipped.
Holds Read this korrent →
The right way to specify a rescue rewrite is a couple of scaling constraints and no new features at all, so that hardware can absorb the growth the team has no time to design for.
Holds
A computer company has to live five to ten years in the future, because a system takes three years to build, two to ramp, and is then used for a decade.
Holds
The fastest-growing companies are not using data well, because they reached enormous scale before they had time to build any of the instrumentation.
Holds
Deploying a new technology at scale takes decades, far longer than the people building it imagine.
Holds
Even a long-horizon deep tech company should chase revenue sooner than it thinks, so that it is valued on its roadmap rather than on its probability of dying.
Holds
Uber's thousands of microservices were not an architectural preference but a survival decision: under that growth only independent, unblocked teams could build fast enough to stay alive.
Holds
Most software rewrites fail and take longer than people expect them to.
Holds
Original thoughts do not scale.
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 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
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
As AI makes it easier to generate code, teams must delete code more aggressively or be overwhelmed by accumulated complexity.
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