Tap a claim on the ring to put it at the centre.
← Code written to be reusable before there is anything reusing it is likely to be reusable in the wrong way.
17 connected korrents · 17 moments from 28 May 2014 to 23 Sept 2026.
Everything filed under software quality
software quality
Everything filed under design
design
Everything filed under software performance
software performance
Everything filed under open source
open source
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: Code written to be reusable before there is anything reusing it is likely to be reusable in the wrong way. Code written to be reusable before there is anything reusing it is likely to be reusable in the wrong way. Last stated 12 years ago
28 May 2014
CM
Casey Muratori — holds since 2014-05-28 — tap for who they are
Same subject: Duplication is cheaper than the wrong abstraction, so code should not be made reusable before there are real examples of what the reuse has to do. — tap to centre the map on it Duplication is cheaper than the wrong abstraction, so code should not be made reusable before there are real examples of what the reuse has to do. Last stated 11 years ago
20 Jan 2016
SM
Sandi Metz — holds since 2016-01-20 — tap for who they are
CM
Casey Muratori — holds since 2014-05-28 — tap for who they are
Same subject: You cannot really understand the code you write unless you are also the one operating it. — tap to centre the map on it You cannot really understand the code you write unless you are also the one operating it. Last stated 2 months ago
12 Aug 2026
CM
Charity Majors — holds since 2026-08-12 — tap for who they are
Same subject: Reusable code should take an allocator parameter only if it allocates, and an I/O parameter only if it performs I/O. — tap to centre the map on it Reusable code should take an allocator parameter only if it allocates, and an I/O parameter only if it performs I/O. Last stated 12 months ago
29 Oct 2025
AK
Andrew Kelley — holds since 2025-10-29 — tap for who they are
Same subject: The programming practices taught as best practice are ruinous for performance and should not be followed. — tap to centre the map on it The programming practices taught as best practice are ruinous for performance and should not be followed. Last stated 4 years ago
28 Feb 2023
CM
Casey Muratori — holds since 2023-02-28 — 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 2 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: What trips up newcomers to Rust is not the code but the shape of their data. — tap to centre the map on it What trips up newcomers to Rust is not the code but the shape of their data. Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: Open source code should be used to enable others to remix and reuse — tap to centre the map on it Open source code should be used to enable others to remix and reuse Last stated 4 years ago
18 Oct 2022
DH
David Heinemeier Hansson — holds since 2022-10-18 — 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: 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
Code written to be reusable before there is anything reusing it is likely to be reusable in the wrong way.
Holds Read this korrent →
Duplication is cheaper than the wrong abstraction, so code should not be made reusable before there are real examples of what the reuse has to do.
Holds
You cannot really understand the code you write unless you are also the one operating it.
Holds
Reusable code should take an allocator parameter only if it allocates, and an I/O parameter only if it performs I/O.
Holds
The programming practices taught as best practice are ruinous for performance and should not be followed.
Holds
The specific rules taught as clean code are simply bad programming practices, and they get worse when you apply them together.
Holds
What trips up newcomers to Rust is not the code but the shape of their data.
Holds
Open source code should be used to enable others to remix and reuse
Holds
Rewriting software from scratch gives developers the freedom to try techniques they might not otherwise attempt.
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