Tap a claim on the ring to put it at the centre.
← Getting feedback on a flaw early saves far more effort than…
17 connected korrents · 15 moments from 24 Aug 2009 to 23 Sept 2026.
Everything filed under software quality
software quality
Everything filed under product management
product management
Everything filed under humility
humility
Everything filed under vibe coding
vibe coding
Everything filed under open source
open source
Everything filed under patience
patience
Everything filed under vibe coding
vibe coding
Everything filed under design
design 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: Getting feedback on a flaw early saves far more effort than discovering it after building much more on top of it. Getting feedback on a flaw early saves far more effort than discovering it after building much more on top of it. Last stated 5 months ago
19 Jun 2026
BF
Brad Feld — holds since 2026-06-19 — tap for who they are
Same subject: It is better not to spend time crafting the exact perfect solution until you know it works; getting an early version you can play with in the product is a really good milestone. — tap to centre the map on it It is better not to spend time crafting the exact perfect solution until you know it works; getting an early version you can play with in the product is a really good milestone. Last stated 7 months ago
8 Apr 2026
IS
Ian Silber — holds since 2026-04-08 — tap for who they are
Same subject: The first version of a product is usually not great. — tap to centre the map on it The first version of a product is usually not great. Last stated 2 months ago
10 Sept 2026
RS
Robby Stein — holds since 2026-09-10 — tap for who they are
Same subject: A sense of achievement in software survives writing almost none of the code yourself. — tap to centre the map on it A sense of achievement in software survives writing almost none of the code yourself. Last stated 2 months ago
26 Aug 2026
DH
David Heinemeier Hansson — holds since 2026-08-26 — tap for who they are
Same subject: Publishing the source is not the same as developing in the open, and only the second changes how the work actually goes. — tap to centre the map on it Publishing the source is not the same as developing in the open, and only the second changes how the work actually goes. Last stated 6 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — 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 5 months ago
12 Jun 2026
BV
Ben Vinegar — holds since 2026-06-12 — 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 4 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
Same subject: A technical leader should let engineers find the flaw in their own design through leading questions rather than announce it, because a discovered flaw is acted on and a reported one is argued with. — tap to centre the map on it A technical leader should let engineers find the flaw in their own design through leading questions rather than announce it, because a discovered flaw is acted on and a reported one is argued with. Last stated 7 months ago
1 Apr 2026
TP
Thuan Pham — holds since 2026-04-01 — tap for who they are
Same subject: You cannot get real feedback on a new consumer product before shipping the whole thing; feedback starts when somebody spends their own money on it. — tap to centre the map on it You cannot get real feedback on a new consumer product before shipping the whole thing; feedback starts when somebody spends their own money on it. Last stated 5 months ago
7 Jun 2026
TF
Tony Fadell — holds since 2026-06-07 — 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 a month ago
23 Sept 2026
GT
Geoff Teehan — holds since 2026-09-23 — tap for who they are
Same subject: A bug live for one day is better than an app stuck in review for two weeks. — tap to centre the map on it A bug live for one day is better than an app stuck in review for two weeks. Last stated 17 years ago
24 Aug 2009
JH
Joe Hewitt — holds since 2009-08-24 — 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: 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 9 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 3 months ago
19 Aug 2026
JS
Jon Seager — holds since 2026-08-19 — tap for who they are
Same subject: AI-generated code should not count as finished work until a human has reviewed and corrected it. — tap to centre the map on it AI-generated code should not count as finished work until a human has reviewed and corrected it. Last stated 7 months ago
1 Apr 2026
DJ
Daniel Jalkut — holds since 2026-04-01 — 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 8 months ago
10 Mar 2026
JS
Jon Seager — holds since 2026-03-10 — 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 4 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