Tap a claim on the ring to put it at the centre.
← Ship for three to six months with nobody reading the code and the…
17 connected korrents · 13 moments from 17 Sept 2010 to 23 Sept 2026.
Everything filed under vibe coding
vibe coding
Everything filed under software quality
software quality
Everything filed under management
management
Everything filed under simplicity
simplicity
Everything filed under LLMs
LLMs
Everything filed under vibe coding
vibe coding 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: 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. 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: Breaking up a monolith takes years rather than months not because the work is hard but because the business keeps adding to it faster than you can pull pieces out. — tap to centre the map on it Breaking up a monolith takes years rather than months not because the work is hard but because the business keeps adding to it faster than you can pull pieces out. Last stated 7 months ago
1 Apr 2026
TP
Thuan Pham — holds since 2026-04-01 — tap for who they are
Same subject: A product leader writing production code is not the best use of their time, even though they should be able to read the codebase. — tap to centre the map on it A product leader writing production code is not the best use of their time, even though they should be able to read the codebase. Last stated 3 months ago
2 Aug 2026
TV
Tom Verrilli — holds since 2026-08-02 — tap for who they are
Same subject: Deleting code goes unrewarded in software careers, which is part of why teams keep shipping new features instead of removing old ones. — tap to centre the map on it Deleting code goes unrewarded in software careers, which is part of why teams keep shipping new features instead of removing old ones. Last stated 2 months ago
1 Sept 2026
VB
Vicki Boykis — holds since 2026-09-01 — tap for who they are
Same subject: Software is going through a fast-fashion phase where projects are thrown away if nobody uses them at once; builders should have conviction and work on things longer. — tap to centre the map on it Software is going through a fast-fashion phase where projects are thrown away if nobody uses them at once; builders should have conviction and work on things longer. Last stated 4 months ago
12 Jun 2026
BV
Ben Vinegar — holds since 2026-06-12 — tap for who they are
Same subject: Leaving a known production bug unfixed is the right call when the business impact is zero — my vibe-coded service crashes and still has fewer outages than LeetCode. — tap to centre the map on it Leaving a known production bug unfixed is the right call when the business impact is zero — my vibe-coded service crashes and still has fewer outages than LeetCode. Last stated 4 months ago
24 Jun 2026
NE
NeetCode — holds since 2026-06-24 — tap for who they are
Same subject: The current ease of building software with AI will be seen as normal and commonplace within 12 to 24 months, though few realize it yet. — tap to centre the map on it The current ease of building software with AI will be seen as normal and commonplace within 12 to 24 months, though few realize it yet. Last stated 3 months ago
15 Jul 2026
TY
Tynan — holds since 2026-07-15 — tap for who they are
Same subject: It is no longer worth not reading the code in exchange for the occasional two-week hand fix, because the volume of code we can now generate has gone up ten to a hundred times. — tap to centre the map on it It is no longer worth not reading the code in exchange for the occasional two-week hand fix, because the volume of code we can now generate has gone up ten to a hundred times. Last stated 3 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
Same subject: Every project reaches the point where the code is a mess, so starting over to fix that only returns you to the same place later. — tap to centre the map on it Every project reaches the point where the code is a mess, so starting over to fix that only returns you to the same place later. Last stated 16 years ago
17 Sept 2010
DY
Derek Yu — holds since 2010-09-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
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 Read this korrent →
Breaking up a monolith takes years rather than months not because the work is hard but because the business keeps adding to it faster than you can pull pieces out.
Holds
A product leader writing production code is not the best use of their time, even though they should be able to read the codebase.
Holds
Deleting code goes unrewarded in software careers, which is part of why teams keep shipping new features instead of removing old ones.
Holds
Software is going through a fast-fashion phase where projects are thrown away if nobody uses them at once; builders should have conviction and work on things longer.
Holds
Leaving a known production bug unfixed is the right call when the business impact is zero — my vibe-coded service crashes and still has fewer outages than LeetCode.
Holds
The current ease of building software with AI will be seen as normal and commonplace within 12 to 24 months, though few realize it yet.
Holds
It is no longer worth not reading the code in exchange for the occasional two-week hand fix, because the volume of code we can now generate has gone up ten to a hundred times.
Holds
Every project reaches the point where the code is a mess, so starting over to fix that only returns you to the same place later.
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