Tap a claim on the ring to put it at the centre.
← Teams that trade quality for speed well never describe it that way —…
17 connected korrents · 16 moments from 19 Apr 2025 to 23 Sept 2026.
Everything filed under software quality
software quality
Everything filed under design
design
Everything filed under startups
startups
Everything filed under team size
team size
Everything filed under curiosity
curiosity
Everything filed under ambition
ambition
Everything filed under software performance
software performance 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: Teams that trade quality for speed well never describe it that way — they make an explicit, bounded, risk-based decision. Teams that trade quality for speed well never describe it that way — they make an explicit, bounded, risk-based decision. Last stated 7 months ago
22 Mar 2026
NF
Nicole Forsgren — holds since 2026-03-22 — tap for who they are
Same subject: Quality comes from doing irrational things — half of what you do you did not have to do — and almost nobody is willing to operate that way. — tap to centre the map on it Quality comes from doing irrational things — half of what you do you did not have to do — and almost nobody is willing to operate that way. Last stated 5 months ago
27 May 2026
DR
Dax Raad — holds since 2026-05-27 — tap for who they are
Same subject: A company's quality is bounded by its team's quality, and a team's quality is bounded by its founders. — tap to centre the map on it A company's quality is bounded by its team's quality, and a team's quality is bounded by its founders. Last stated a year ago
22 Oct 2025
TP
Tom Preston-Werner — holds since 2025-10-22 — tap for who they are
Same subject: Teams need to create the grounds to take some risk, committing as much iteration to the new thing as was put into the incumbent product. — tap to centre the map on it Teams need to create the grounds to take some risk, committing as much iteration to the new thing as was put into the incumbent product. Last stated 5 months ago
12 May 2026
KB
Katarina Batina — holds since 2026-05-12 — tap for who they are
Same subject: A small team is not a compromise: it is the only size at which everyone is in the room for every decision, including the ones outside their discipline. — tap to centre the map on it A small team is not a compromise: it is the only size at which everyone is in the room for every decision, including the ones outside their discipline. Last stated 7 months ago
11 Mar 2026
JK
Jeff Kaplan — holds since 2026-03-11 — tap for who they are
Same subject: Good teams keep asking what could make something better and how it could be different, but not just for difference's sake. — tap to centre the map on it Good teams keep asking what could make something better and how it could be different, but not just for difference's sake. Last stated 4 weeks ago
23 Sept 2026
GT
Geoff Teehan — holds since 2026-09-23 — tap for who they are
Same subject: People who can reliably make outcomes happen without oversight are rare and are the real bottleneck on how much an organization can take on at once. — tap to centre the map on it People who can reliably make outcomes happen without oversight are rare and are the real bottleneck on how much an organization can take on at once. Last stated 2 years ago
19 Apr 2025
BK
Ben Kuhn — holds since 2025-04-19 — tap for who they are
Same subject: Designers should define quality and share it as a workflow anyone on the team can use, in a way that is additive, teaching and guiding rather than stopping. — tap to centre the map on it Designers should define quality and share it as a workflow anyone on the team can use, in a way that is additive, teaching and guiding rather than stopping. Last stated 4 months ago
8 Jul 2026
MC
Meaghan Choi — holds since 2026-07-08 — tap for who they are
Same subject: Everyone on a team who makes architectural decisions must understand performance, because a codebase that can be optimized later only ends up that way on purpose. — tap to centre the map on it Everyone on a team who makes architectural decisions must understand performance, because a codebase that can be optimized later only ends up that way on purpose. Last stated 2 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-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: 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
Teams that trade quality for speed well never describe it that way — they make an explicit, bounded, risk-based decision.
Holds Read this korrent →
Quality comes from doing irrational things — half of what you do you did not have to do — and almost nobody is willing to operate that way.
Holds
A company's quality is bounded by its team's quality, and a team's quality is bounded by its founders.
Holds
Teams need to create the grounds to take some risk, committing as much iteration to the new thing as was put into the incumbent product.
Holds
A small team is not a compromise: it is the only size at which everyone is in the room for every decision, including the ones outside their discipline.
Holds
Good teams keep asking what could make something better and how it could be different, but not just for difference's sake.
Holds
People who can reliably make outcomes happen without oversight are rare and are the real bottleneck on how much an organization can take on at once.
Holds
Designers should define quality and share it as a workflow anyone on the team can use, in a way that is additive, teaching and guiding rather than stopping.
Holds
Everyone on a team who makes architectural decisions must understand performance, because a codebase that can be optimized later only ends up that way on purpose.
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