Tap a claim on the ring to put it at the centre.
← A small software package with good intentions can accumulate so many…
17 connected korrents · 17 moments from 11 Dec 2021 to 23 Sept 2026.
Everything filed under software quality
software quality
Everything filed under open source
open source
Everything filed under design
design
Everything filed under software performance
software performance
Everything filed under cybersecurity
cybersecurity
Everything filed under startups
startups 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: A small software package with good intentions can accumulate so many dependents and dependencies that it becomes a vector for bloat and malfeasance. A small software package with good intentions can accumulate so many dependents and dependencies that it becomes a vector for bloat and malfeasance. Last stated 2 years ago
13 Feb 2025
RP
Rob Pike — holds since 2025-02-13 — tap for who they are
Same subject: A software ecosystem made of many tiny modules from many different authors is unsafe against malicious actors and should give way to larger, vetted libraries. — tap to centre the map on it A software ecosystem made of many tiny modules from many different authors is unsafe against malicious actors and should give way to larger, vetted libraries. Last stated 2 months ago
14 Aug 2026
TM
Tom MacWright — holds since 2026-08-14 — tap for who they are
Same subject: Merging the tempting extra feature means adopting a pile of code that neither its author nor the maintainer really understands. — tap to centre the map on it Merging the tempting extra feature means adopting a pile of code that neither its author nor the maintainer really understands. Last stated 2 months ago
10 Aug 2026
PS
Peter Steinberger — holds since 2026-08-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 3 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: Making programming easier for more people has caused software to become bloated, slow and hard to manage. — tap to centre the map on it Making programming easier for more people has caused software to become bloated, slow and hard to manage. Last stated 9 months ago
15 Jan 2026
NP
Nikita Prokopov — holds since 2026-01-15 — tap for who they are
Same subject: A business succeeds through a small number of highly effective distribution channels, not many mediocre ones. — tap to centre the map on it A business succeeds through a small number of highly effective distribution channels, not many mediocre ones. Last stated 3 years ago
17 Feb 2024
AW
Adam Wiggins — holds since 2024-02-17 — tap for who they are
Same subject: Just because something can be built as a function does not mean it needs to be, and adding it brings a lot of product bloat and complexity. — tap to centre the map on it Just because something can be built as a function does not mean it needs to be, and adding it brings a lot of product bloat and complexity. Last stated 4 months ago
8 Jul 2026
MC
Meaghan Choi — holds since 2026-07-08 — tap for who they are
Same subject: Bloated, slow software is caused by a lack of engineering care, not by the choice of technology stack. — tap to centre the map on it Bloated, slow software is caused by a lack of engineering care, not by the choice of technology stack. Last stated 8 months ago
3 Mar 2026
NP
Nikita Prokopov — holds since 2026-03-03 — tap for who they are
Same subject: A business making hundreds of millions from an open source project owes it money or contribution, and can be refused its trademarks if it gives neither. — tap to centre the map on it A business making hundreds of millions from an open source project owes it money or contribution, and can be refused its trademarks if it gives neither. Last stated 2 years ago
26 Sept 2024
MM
Matt Mullenweg — holds since 2024-09-26 — tap for who they are
Same subject: A codec does not really exist until everyone can decode it. — tap to centre the map on it A codec does not really exist until everyone can decode it. Last stated 5 months ago
31 May 2026
JK
Jean-Baptiste Kempf — holds since 2026-05-31 — tap for who they are
Same subject: A company that will not accept a project’s terms is free to go and use a more permissive project instead. — tap to centre the map on it A company that will not accept a project’s terms is free to go and use a more permissive project instead. Last stated 2 years ago
26 Sept 2024
MM
Matt Mullenweg — holds since 2024-09-26 — 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: An app used every day should be built by a thoughtful team of engineers rather than one-shotted with Claude. — tap to centre the map on it An app used every day should be built by a thoughtful team of engineers rather than one-shotted with Claude. Last stated 5 months ago
26 May 2026
AM
Andy Madrick — holds since 2026-05-26 — tap for who they are
Same subject: An open-weight model is already all anyone needs; it is as good as the frontier models. — tap to centre the map on it An open-weight model is already all anyone needs; it is as good as the frontier models. Last stated 2 months ago
26 Aug 2026
DH
David Heinemeier Hansson — no longer holds since 2026-08-26 — tap for who they are
Same subject: By 2027, open-weight AI models more powerful than today's frontier systems will be downloadable by any country or well-resourced non-state group. — tap to centre the map on it By 2027, open-weight AI models more powerful than today's frontier systems will be downloadable by any country or well-resourced non-state group. Last stated 2 months ago
19 Aug 2026
DT
Derek Thompson — holds since 2026-08-19 — tap for who they are
At the centre
A small software package with good intentions can accumulate so many dependents and dependencies that it becomes a vector for bloat and malfeasance.
Holds Read this korrent →
A software ecosystem made of many tiny modules from many different authors is unsafe against malicious actors and should give way to larger, vetted libraries.
Holds
Merging the tempting extra feature means adopting a pile of code that neither its author nor the maintainer really understands.
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
Making programming easier for more people has caused software to become bloated, slow and hard to manage.
Holds
A business succeeds through a small number of highly effective distribution channels, not many mediocre ones.
Holds
Just because something can be built as a function does not mean it needs to be, and adding it brings a lot of product bloat and complexity.
Holds
Bloated, slow software is caused by a lack of engineering care, not by the choice of technology stack.
Holds
A business making hundreds of millions from an open source project owes it money or contribution, and can be refused its trademarks if it gives neither.
Holds
A codec does not really exist until everyone can decode it.
Holds
A company that will not accept a project’s terms is free to go and use a more permissive project instead.
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
An app used every day should be built by a thoughtful team of engineers rather than one-shotted with Claude.
Holds
An open-weight model is already all anyone needs; it is as good as the frontier models.
No longer holds
By 2027, open-weight AI models more powerful than today's frontier systems will be downloadable by any country or well-resourced non-state group.
Holds