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 on record from 17 Jun 2018 to 3 Sept 2026.
Everything filed under software performance
software performance
Everything filed under team size
team size
Everything filed under code generation
code generation
Everything filed under hiring
hiring
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: 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 6 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 3 months ago
27 May 2026
DR
Dax Raad — holds since 2026-05-27 — 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 6 months ago
11 Mar 2026
JK
Jeff Kaplan — holds since 2026-03-11 — 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 weeks ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: Spreading scarce hiring evenly across every team that needs it is indecision dressed as fairness; staff one team to health at a time. — tap to centre the map on it Spreading scarce hiring evenly across every team that needs it is indecision dressed as fairness; staff one team to health at a time. Last stated 8 years ago
17 Jun 2018
WL
Will Larson — holds since 2018-06-17 — tap for who they are
Same subject: Cruft is not carelessness: even the best teams inevitably create it, because the right design is only visible once the software has been built. — tap to centre the map on it Cruft is not carelessness: even the best teams inevitably create it, because the right design is only visible once the software has been built. Last stated 7 years ago
29 May 2019
MF
Martin Fowler — holds since 2019-05-29 — tap for who they are
Same subject: Fun can be a product's differentiator, even when the team thinks that is an absurd thing to compete on. — tap to centre the map on it Fun can be a product's differentiator, even when the team thinks that is an absurd thing to compete on. Last stated 11 months ago
16 Oct 2025
DF
Dylan Field — holds since 2025-10-16 — tap for who they are
Same subject: Companies do not have sufficient incentives to mitigate the major risks of AI, and competition between them is driving corner-cutting. — tap to centre the map on it Companies do not have sufficient incentives to mitigate the major risks of AI, and competition between them is driving corner-cutting. Last stated 2 years ago
15 Feb 2025
MB
Miles Brundage — holds since 2025-02-15 — tap for who they are
Same subject: Systematising principled decision-making with AI is now the line between staying competitive and not; there is no position in between. — tap to centre the map on it Systematising principled decision-making with AI is now the line between staying competitive and not; there is no position in between. Last stated 3 months ago
10 Jun 2026
RD
Ray Dalio — holds since 2026-06-10 — tap for who they are
Same subject: "Is the page loaded?" was never a real question, and web performance only became measurable once it was broken into the distinct moments a user actually notices. — tap to centre the map on it "Is the page loaded?" was never a real question, and web performance only became measurable once it was broken into the distinct moments a user actually notices. Last stated 3 weeks ago
19 Aug 2026
AO
Addy Osmani — holds since 2026-08-19 — tap for who they are
Same subject: "Optimize it later" would be safe advice only if every engineer already knew how to avoid the architectural mistakes that no later optimization can remove. — tap to centre the map on it "Optimize it later" would be safe advice only if every engineer already knew how to avoid the architectural mistakes that no later optimization can remove. Last stated 2 weeks ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: A 300-millisecond response budget is not an achievement but an admission: 300 milliseconds is an eternity in computing, and a product pitching it shows how far the bar has fallen. — tap to centre the map on it A 300-millisecond response budget is not an achievement but an admission: 300 milliseconds is an eternity in computing, and a product pitching it shows how far the bar has fallen. Last stated 2 weeks ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: A group of fewer than four people is not a team: it behaves like a set of individuals, and a single departure knocks it back into maintenance. — tap to centre the map on it A group of fewer than four people is not a team: it behaves like a set of individuals, and a single departure knocks it back into maintenance. Last stated 8 years ago
14 Jul 2018
WL
Will Larson — holds since 2018-07-14 — tap for who they are
Same subject: A healthy on-call rotation needs at least six engineers for every alert to get an engineer's full attention. — tap to centre the map on it A healthy on-call rotation needs at least six engineers for every alert to get an engineer's full attention. Last stated 5 days ago
3 Sept 2026
GO
Gergely Orosz — holds since 2026-09-03 — tap for who they are
Same subject: A small team should start from an open-source generalist policy and fine-tune it on day one, rather than scale up its own specialist models first. — tap to centre the map on it A small team should start from an open-source generalist policy and fine-tune it on day one, rather than scale up its own specialist models first. Last stated 4 weeks ago
12 Aug 2026
CF
Chelsea Finn — holds since 2026-08-12 — tap for who they are
Same subject: AI acceleration threatens 'less software': without the constraint of scarce hours, even 37signals will likely build too much. — tap to centre the map on it AI acceleration threatens 'less software': without the constraint of scarce hours, even 37signals will likely build too much. Last stated a month ago
26 Jul 2026
DH
David Heinemeier Hansson — holds since 2026-07-26 — tap for who they are
Same subject: AI-written code makes formal proof necessary, because human review of all that generated code becomes the bottleneck. — tap to centre the map on it AI-written code makes formal proof necessary, because human review of all that generated code becomes the bottleneck. Last stated 5 months ago
22 Apr 2026
MK
Martin Kleppmann — holds since 2026-04-22 — tap for who they are
Same subject: Code and files generated by tools are pollution: hand-writing them is worth the effort because the bloat slows everything down for everyone. — tap to centre the map on it Code and files generated by tools are pollution: hand-writing them is worth the effort because the bloat slows everything down for everyone. Last stated 7 years ago
15 Oct 2019
DS
Derek Sivers — holds since 2019-10-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 NF Nicole ForsgrenRead 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 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 JK Jeff Kaplan
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 CM Casey Muratori
Spreading scarce hiring evenly across every team that needs it is indecision dressed as fairness; staff one team to health at a time.
Holds WL Will Larson
Cruft is not carelessness: even the best teams inevitably create it, because the right design is only visible once the software has been built.
Holds MF Martin Fowler
Fun can be a product's differentiator, even when the team thinks that is an absurd thing to compete on.
Holds DF Dylan Field
Companies do not have sufficient incentives to mitigate the major risks of AI, and competition between them is driving corner-cutting.
Holds MB Miles Brundage
Systematising principled decision-making with AI is now the line between staying competitive and not; there is no position in between.
Holds
"Is the page loaded?" was never a real question, and web performance only became measurable once it was broken into the distinct moments a user actually notices.
Holds AO Addy Osmani
"Optimize it later" would be safe advice only if every engineer already knew how to avoid the architectural mistakes that no later optimization can remove.
Holds CM Casey Muratori
A 300-millisecond response budget is not an achievement but an admission: 300 milliseconds is an eternity in computing, and a product pitching it shows how far the bar has fallen.
Holds CM Casey Muratori
A group of fewer than four people is not a team: it behaves like a set of individuals, and a single departure knocks it back into maintenance.
Holds WL Will Larson
A healthy on-call rotation needs at least six engineers for every alert to get an engineer's full attention.
Holds
A small team should start from an open-source generalist policy and fine-tune it on day one, rather than scale up its own specialist models first.
Holds CF Chelsea Finn
AI acceleration threatens 'less software': without the constraint of scarce hours, even 37signals will likely build too much.
Holds
AI-written code makes formal proof necessary, because human review of all that generated code becomes the bottleneck.
Holds MK Martin Kleppmann
Code and files generated by tools are pollution: hand-writing them is worth the effort because the bloat slows everything down for everyone.
Holds