Tap a claim on the ring to put it at the centre.
← Mutable stateful objects are the new spaghetti code: hard to…
17 connected korrents · 17 moments from 1 Feb 1996 to 4 Oct 2026.
Everything filed under software quality
software quality
Everything filed under taste
taste
Everything filed under innovation
innovation
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: Mutable stateful objects are the new spaghetti code: hard to understand, hard to test and hard to reason about. Mutable stateful objects are the new spaghetti code: hard to understand, hard to test and hard to reason about. Last stated 9 years ago
by 2 Jan 2018
RH
Rich Hickey — holds since 2018-01-02 — tap for who they are
Same subject: Enforcing safe mutable value semantics (e.g. via borrow-checking) is far easier to do cheaply with a static type system than with a dynamic one. — tap to centre the map on it Enforcing safe mutable value semantics (e.g. via borrow-checking) is far easier to do cheaply with a static type system than with a dynamic one. Last stated 6 months ago
22 Apr 2026
JB
Jamie Brandon — holds since 2026-04-22 — tap for who they are
Same subject: Rust code is very pretty to look at, though the author suspects few others share this view. — tap to centre the map on it Rust code is very pretty to look at, though the author suspects few others share this view. Last stated 4 weeks ago
24 Sept 2026
AR
Armin Ronacher — holds since 2026-09-24 — 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: 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: Once objects are understood, it is clear that all software will eventually be written using them; the timing and the winners can be argued, the inevitability cannot. — tap to centre the map on it Once objects are understood, it is clear that all software will eventually be written using them; the timing and the winners can be argued, the inevitability cannot. Last stated 31 years ago
1 Feb 1996
SJ
Steve Jobs — holds since 1996-02-01 — tap for who they are
Same subject: Code is procedurally oriented rather than object-oriented: objects are just constructs that emerge to let procedures be reused. — tap to centre the map on it Code is procedurally oriented rather than object-oriented: objects are just constructs that emerge to let procedures be reused. Last stated 12 years ago
28 May 2014
CM
Casey Muratori — holds since 2014-05-28 — tap for who they are
Same subject: Coding models are worst at exactly the thing an AI research explosion would need: code that has never been written before. — tap to centre the map on it Coding models are worst at exactly the thing an AI research explosion would need: code that has never been written before. Last stated a year ago
17 Oct 2025
AK
Andrej Karpathy — holds since 2025-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 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
Mutable stateful objects are the new spaghetti code: hard to understand, hard to test and hard to reason about.
Holds Read this korrent →
Enforcing safe mutable value semantics (e.g. via borrow-checking) is far easier to do cheaply with a static type system than with a dynamic one.
Holds
Rust code is very pretty to look at, though the author suspects few others share this view.
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
The economic trade-off between language verbosity and programmer cost has changed.
Holds
Once objects are understood, it is clear that all software will eventually be written using them; the timing and the winners can be argued, the inevitability cannot.
Holds
Code is procedurally oriented rather than object-oriented: objects are just constructs that emerge to let procedures be reused.
Holds
Coding models are worst at exactly the thing an AI research explosion would need: code that has never been written before.
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