Tap a claim on the ring to put it at the centre.
← Rewriting mature C code from scratch is expensive, risky, and rarely produces clear improvements.
17 connected korrents · 18 moments from 22 Mar 2025 to 17 Oct 2026.
Everything filed under software quality
software quality
Everything filed under code generation
code generation
Everything filed under coding agents
coding agents
Everything filed under innovation
innovation 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: Rewriting mature C code from scratch is expensive, risky, and rarely produces clear improvements. Rewriting mature C code from scratch is expensive, risky, and rarely produces clear improvements. Last stated 2 months ago
19 Aug 2026
JS
Jon Seager — holds since 2026-08-19 — tap for who they are
Same subject: Rewriting software from scratch gives developers the freedom to try techniques they might not otherwise attempt. — tap to centre the map on it Rewriting software from scratch gives developers the freedom to try techniques they might not otherwise attempt. Last stated 10 months ago
29 Dec 2025
AP
Aaron Patterson — holds since 2025-12-29 — 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: Most organisations are bottlenecked on ideas, vision and taste rather than on implementation, so making code cheap does not make them productive. — tap to centre the map on it Most organisations are bottlenecked on ideas, vision and taste rather than on implementation, so making code cheap does not make them productive. Last stated 2 months ago
26 Aug 2026
DH
David Heinemeier Hansson — holds since 2026-08-26 — tap for who they are
Same subject: The economic trade-off between language verbosity and programmer cost has changed. — tap to centre the map on it The economic trade-off between language verbosity and programmer cost has changed. Last stated 3 weeks ago
4 Oct 2026
DH
David Heinemeier Hansson — holds since 2026-10-04 — tap for who they are
Same subject: AI-generated code does not reach the structural quality of the best hand-written software. — tap to centre the map on it AI-generated code does not reach the structural quality of the best hand-written software. Last stated 5 months ago
7 Jun 2026
SS
Salvatore Sanfilippo — holds since 2026-06-07 — tap for who they are
Same subject: A year from now every coding model on the market will still take a bad instruction at face value and go fix the listed issues, where a human senior engineer would insist on a rewrite. — tap to centre the map on it A year from now every coding model on the market will still take a bad instruction at face value and go fix the listed issues, where a human senior engineer would insist on a rewrite. Last stated 5 months ago
24 May 2026
DS
Dan Shipper — holds since 2026-05-24 — tap for who they are
Same subject: AI-generated code is not fully reliable and typically needs significant manual effort to keep it working correctly. — tap to centre the map on it AI-generated code is not fully reliable and typically needs significant manual effort to keep it working correctly. Last stated 4 months ago
16 Jun 2026
SW
Stephen Wolfram — holds since 2026-06-16 — tap for who they are
Same subject: It is now much faster and easier to change code than it was years ago. — tap to centre the map on it It is now much faster and easier to change code than it was years ago. Last stated 5 days ago
17 Oct 2026
TB
Thorsten Ball — holds since 2026-10-17 — 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 feature added to a codebase is extremely difficult to remove once other code is built on top of it. — tap to centre the map on it A feature added to a codebase is extremely difficult to remove once other code is built on top of it. Last stated 2 months ago
1 Sept 2026
VB
Vicki Boykis — holds since 2026-09-01 — 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 a month ago
14 Sept 2026
JS
Jason Snell — holds since 2026-09-14 — tap for who they are
Same subject: CMake tooling is missing a linter that could statically catch most CMakeLists.txt mistakes. — tap to centre the map on it CMake tooling is missing a linter that could statically catch most CMakeLists.txt mistakes. Last stated a month ago
20 Sept 2026
CW
Chris Wellons — holds since 2026-09-20 — tap for who they are
Same subject: Comparing code coverage between passing and failing test runs is a cheap, effective way to localize a bug quickly. — tap to centre the map on it Comparing code coverage between passing and failing test runs is a cheap, effective way to localize a bug quickly. Last stated a year ago
25 Apr 2025
RC
Russ Cox — holds since 2025-04-25 — tap for who they are
Same subject: Everyone is rethinking code reviews, deploys, and possibly observability — tap to centre the map on it Everyone is rethinking code reviews, deploys, and possibly observability Last stated a month ago
16 Sept 2026
GO
Gergely Orosz — holds since 2026-09-16 — tap for who they are
Same subject: Coding with an AI assistant slides from copiloting into autopiloting, and the bugs that follow are hard to trace. — tap to centre the map on it Coding with an AI assistant slides from copiloting into autopiloting, and the bugs that follow are hard to trace. Last stated 2 years ago
22 Mar 2025
TH
ThePrimeagen — holds since 2025-03-22 — tap for who they are
Same subject: Ship for three to six months with nobody reading the code and the codebase gets so bad that starting over is easier than fixing it — we ran a lights-off software factory and shut it down. — tap to centre the map on it Ship for three to six months with nobody reading the code and the codebase gets so bad that starting over is easier than fixing it — we ran a lights-off software factory and shut it down. Last stated 3 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
Same subject: The judgement call about whether to absorb a hack is distorted right now, because the agent will simply do the hacky thing and deal with the consequences for you. — tap to centre the map on it The judgement call about whether to absorb a hack is distorted right now, because the agent will simply do the hacky thing and deal with the consequences for you. Last stated 5 months ago
27 May 2026
DR
Dax Raad — holds since 2026-05-27 — tap for who they are
At the centre
Rewriting mature C code from scratch is expensive, risky, and rarely produces clear improvements.
Holds Read this korrent →
Rewriting software from scratch gives developers the freedom to try techniques they might not otherwise attempt.
Holds
Most software rewrites fail and take longer than people expect them to.
Holds
Most organisations are bottlenecked on ideas, vision and taste rather than on implementation, so making code cheap does not make them productive.
Holds
The economic trade-off between language verbosity and programmer cost has changed.
Holds
AI-generated code does not reach the structural quality of the best hand-written software.
Holds
A year from now every coding model on the market will still take a bad instruction at face value and go fix the listed issues, where a human senior engineer would insist on a rewrite.
Holds
AI-generated code is not fully reliable and typically needs significant manual effort to keep it working correctly.
Holds
It is now much faster and easier to change code than it was years ago.
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 feature added to a codebase is extremely difficult to remove once other code is built on top of it.
Holds
A feature shipped in a product's official release is fair to judge, regardless of whether the company labels it a beta.
Holds
CMake tooling is missing a linter that could statically catch most CMakeLists.txt mistakes.
Holds
Comparing code coverage between passing and failing test runs is a cheap, effective way to localize a bug quickly.
Holds
Everyone is rethinking code reviews, deploys, and possibly observability
Holds
Coding with an AI assistant slides from copiloting into autopiloting, and the bugs that follow are hard to trace.
Holds
Ship for three to six months with nobody reading the code and the codebase gets so bad that starting over is easier than fixing it — we ran a lights-off software factory and shut it down.
Holds
The judgement call about whether to absorb a hack is distorted right now, because the agent will simply do the hacky thing and deal with the consequences for you.
Holds