Tap a claim on the ring to put it at the centre.
← Software should be fast, knowable, and owned by the person using it
17 connected korrents · 17 moments from 1 Jul 2019 to 2 Oct 2026.
Everything filed under software performance
software performance
Everything filed under coding agents
coding agents
Everything filed under SaaS
SaaS
Everything filed under agency
agency
Everything filed under software quality
software quality
Everything filed under developer tools
developer tools 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: Software should be fast, knowable, and owned by the person using it Software should be fast, knowable, and owned by the person using it Last stated 8 months ago
1 Mar 2026
CM
Craig Mod — holds since 2026-03-01 — tap for who they are
Same subject: People should make software that exactly meets their own and their friends' needs. — tap to centre the map on it People should make software that exactly meets their own and their friends' needs. Last stated 2 months ago
30 Aug 2026
TS
Tara Seshan — holds since 2026-08-30 — tap for who they are
Same subject: Most people will keep paying for software rather than build and maintain their own. — tap to centre the map on it Most people will keep paying for software rather than build and maintain their own. Last stated a year ago
7 Oct 2025
NE
Nat Eliason — holds since 2025-10-07 — tap for who they are
Same subject: Questions whether software that works, performs well, has no bugs, is understood, and can later be modified by an agent should be called slop. — tap to centre the map on it Questions whether software that works, performs well, has no bugs, is understood, and can later be modified by an agent should be called slop. Last stated 3 weeks ago
2 Oct 2026
TB
Thorsten Ball — holds since 2026-10-02 — 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: Software only gets good by being used a lot by the people building it, so time spent inside coding agents instead of the app is time that makes the app worse. — tap to centre the map on it Software only gets good by being used a lot by the people building it, so time spent inside coding agents instead of the app is time that makes the app worse. Last stated a month ago
6 Sept 2026
BV
Ben Vinegar — holds since 2026-09-06 — tap for who they are
Same subject: Software should be allowed to be finished, the way a knife or an album is, and the customer who bought the old version should get to keep it. — tap to centre the map on it Software should be allowed to be finished, the way a knife or an album is, and the customer who bought the old version should get to keep it. Last stated 3 months ago
26 Jul 2026
DH
David Heinemeier Hansson — holds since 2026-07-26 — tap for who they are
Same subject: Even as AI makes building software easy, people will still prefer to buy some software off-the-shelf rather than build their own. — tap to centre the map on it Even as AI makes building software easy, people will still prefer to buy some software off-the-shelf rather than build their own. Last stated 3 months ago
11 Jul 2026
JF
Jason Fried — holds since 2026-03-20 — tap for who they are
JJ
Justin Jackson — holds since 2026-07-11 — tap for who they are
Same subject: Fast software is not always good software, but slow software is rarely able to rise to greatness, because not breaking flow is an axiom of great tools. — tap to centre the map on it Fast software is not always good software, but slow software is rarely able to rise to greatness, because not breaking flow is an axiom of great tools. Last stated 7 years ago
1 Jul 2019
CM
Craig Mod — holds since 2019-07-01 — 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 2 months 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 months 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 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: A profiler measures time already spent in an operation, not how much time would be saved by optimizing it. — tap to centre the map on it A profiler measures time already spent in an operation, not how much time would be saved by optimizing it. Last stated 3 years ago
18 Dec 2023
NE
Nelson Elhage — holds since 2023-12-18 — tap for who they are
Same subject: A tool's speed comes primarily from its design decisions rather than the programming language it is written in. — tap to centre the map on it A tool's speed comes primarily from its design decisions rather than the programming language it is written in. Last stated 10 months ago
29 Dec 2025
AP
Aaron Patterson — holds since 2025-12-29 — tap for who they are
Same subject: Monitoring tools that do periodic work can themselves cause the latency outliers they were installed to diagnose. — tap to centre the map on it Monitoring tools that do periodic work can themselves cause the latency outliers they were installed to diagnose. Last stated a year ago
3 Aug 2025
BG
Brendan Gregg — holds since 2025-08-03 — tap for who they are
Same subject: Compiler mechanisms that force a required optimization to occur, rather than relying on incidental compiler behavior, are a more robust way to write performance-sensitive code. — tap to centre the map on it Compiler mechanisms that force a required optimization to occur, rather than relying on incidental compiler behavior, are a more robust way to write performance-sensitive code. Last stated 2 years ago
9 Mar 2025
NE
Nelson Elhage — holds since 2025-03-09 — tap for who they are
Same subject: What clean-code polymorphism really costs you is not the virtual call but the optimizations the compiler can no longer perform once it cannot see what runs. — tap to centre the map on it What clean-code polymorphism really costs you is not the virtual call but the optimizations the compiler can no longer perform once it cannot see what runs. Last stated 2 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: A compiler that also serves an IDE has to be lazy and deferred throughout — a different way of building compilers from the one the textbooks teach. — tap to centre the map on it A compiler that also serves an IDE has to be lazy and deferred throughout — a different way of building compilers from the one the textbooks teach. Last stated 5 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
At the centre
Software should be fast, knowable, and owned by the person using it
Holds Read this korrent →
People should make software that exactly meets their own and their friends' needs.
Holds
Most people will keep paying for software rather than build and maintain their own.
Holds
Questions whether software that works, performs well, has no bugs, is understood, and can later be modified by an agent should be called slop.
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
Software only gets good by being used a lot by the people building it, so time spent inside coding agents instead of the app is time that makes the app worse.
Holds
Software should be allowed to be finished, the way a knife or an album is, and the customer who bought the old version should get to keep it.
Holds
Even as AI makes building software easy, people will still prefer to buy some software off-the-shelf rather than build their own.
Holds
Fast software is not always good software, but slow software is rarely able to rise to greatness, because not breaking flow is an axiom of great tools.
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
"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
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
A profiler measures time already spent in an operation, not how much time would be saved by optimizing it.
Holds
A tool's speed comes primarily from its design decisions rather than the programming language it is written in.
Holds
Monitoring tools that do periodic work can themselves cause the latency outliers they were installed to diagnose.
Holds
Compiler mechanisms that force a required optimization to occur, rather than relying on incidental compiler behavior, are a more robust way to write performance-sensitive code.
Holds
What clean-code polymorphism really costs you is not the virtual call but the optimizations the compiler can no longer perform once it cannot see what runs.
Holds
A compiler that also serves an IDE has to be lazy and deferred throughout — a different way of building compilers from the one the textbooks teach.
Holds