Tap a claim on the ring to put it at the centre.
← N+1 queries are probably the second most common cause of poor web app performance, after forgotten indexes.
17 connected korrents · 15 moments from 28 Feb 2023 to 6 Nov 2026.
Everything filed under software performance
software performance
Everything filed under benchmarks
benchmarks
Everything filed under compilers
compilers
Everything filed under developer tools
developer tools
Everything filed under Ruby
Ruby
Everything filed under LLMs
LLMs
Everything filed under JavaScript
JavaScript
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: N+1 queries are probably the second most common cause of poor web app performance, after forgotten indexes.
N+1 queries are probably the second most common cause of poor web app performance, after forgotten indexes.
Last stated 2 years ago
28 May 2024
BL
Brandur Leach — holds since 2024-05-28 — tap for who they are
Same subject: When diagnosing a performance problem, starting with a CPU profile is more useful than checking database queries first. — tap to centre the map on it
When diagnosing a performance problem, starting with a CPU profile is more useful than checking database queries first.
Last stated 4 months ago
21 Jul 2026
JE
Julia Evans — holds since 2026-07-21 — tap for who they are
Same subject: The steady stream of "we had to rewrite the whole thing because it was too slow" engineering blog posts is the proof that deferring performance to hotspot optimization does not work. — tap to centre the map on it
The steady stream of "we had to rewrite the whole thing because it was too slow" engineering blog posts is the proof that deferring performance to hotspot optimization does not work.
Last stated 3 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: Garbage collection is a problem for backends too, not only for embedded code: a collection that lands on an incoming request is a latency spike. — tap to centre the map on it
Garbage collection is a problem for backends too, not only for embedded code: a collection that lands on an incoming request is a latency spike.
Last stated 6 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: Go is no less susceptible to N+1 queries than a metaprogramming-heavy language like Ruby, despite its verbosity. — tap to centre the map on it
Go is no less susceptible to N+1 queries than a metaprogramming-heavy language like Ruby, despite its verbosity.
Last stated 2 years ago
28 May 2024
BL
Brandur Leach — holds since 2024-05-28 — tap for who they are
Same subject: Performance work used to mean half a day reading traces before writing a single fix, and language models have collapsed that step to minutes. — tap to centre the map on it
Performance work used to mean half a day reading traces before writing a single fix, and language models have collapsed that step to minutes.
Last stated 3 months ago
19 Aug 2026
AO
Addy Osmani — holds since 2026-08-19 — tap for who they are
Same subject: The mass adoption of React and single-page-app architecture across nearly all web apps was driven by trend-following rather than technical fit, producing fragile, scripting-dependent software. — tap to centre the map on it
The mass adoption of React and single-page-app architecture across nearly all web apps was driven by trend-following rather than technical fit, producing fragile, scripting-dependent software.
Last stated 7 months ago
25 Apr 2026
PH
Phil Hagelberg — holds since 2026-04-25 — tap for who they are
Same subject: The programming practices taught as best practice are ruinous for performance and should not be followed. — tap to centre the map on it
The programming practices taught as best practice are ruinous for performance and should not be followed.
Last stated 4 years ago
28 Feb 2023
CM
Casey Muratori — holds since 2023-02-28 — tap for who they are
Same subject: Bloated, slow software is caused by a lack of engineering care, not by the choice of technology stack. — tap to centre the map on it
Bloated, slow software is caused by a lack of engineering care, not by the choice of technology stack.
Last stated 9 months ago
3 Mar 2026
NP
Nikita Prokopov — holds since 2026-03-03 — tap for who they are
Same subject: A coding agent should probably open in your project folder rather than in the process's parent directory. — tap to centre the map on it
A coding agent should probably open in your project folder rather than in the process's parent directory.
Last stated 2 weeks ago
6 Nov 2026
SH
Scott Hanselman — holds since 2026-11-06 — tap for who they are
Same subject: A coding AI that integrates only with its own vendor's tools will be very limited compared with one that draws on all the tools you use. — tap to centre the map on it
A coding AI that integrates only with its own vendor's tools will be very limited compared with one that draws on all the tools you use.
Last stated 3 years ago
16 Mar 2024
QS
Quinn Slack — holds since 2024-03-16 — 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 6 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting. — tap to centre the map on it
A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting.
Last stated 6 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: A programming language is not a compiler but an experience: editing, running, debugging and the runtime library all have to fit together as one cycle. — tap to centre the map on it
A programming language is not a compiler but an experience: editing, running, debugging and the runtime library all have to fit together as one cycle.
Last stated 6 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: A speed difference between languages that share the LLVM backend measures the benchmark author, not the languages. — tap to centre the map on it
A speed difference between languages that share the LLVM backend measures the benchmark author, not the languages.
Last stated 2 years ago
22 Mar 2025
TH
ThePrimeagen — holds since 2025-03-22 — tap for who they are
Same subject: 'Everyone gets it wrong sometimes' is a bad argument when assessing track records. — tap to centre the map on it
'Everyone gets it wrong sometimes' is a bad argument when assessing track records.
Last stated 4 months ago
2 Aug 2026
AK
Adam Kucharski — holds since 2026-08-02 — tap for who they are
Same subject: A benchmark result should be reported under a stated budget, or as a curve against test-time compute — never as a single number. — tap to centre the map on it
A benchmark result should be reported under a stated budget, or as a curve against test-time compute — never as a single number.
Last stated 5 months ago
26 Jun 2026
NB
Noam Brown — holds since 2026-06-26 — tap for who they are
Same subject: A benchmark that ranks Claude Code last while it stays first in use is measuring the wrong thing, and has been for a year. — tap to centre the map on it
A benchmark that ranks Claude Code last while it stays first in use is measuring the wrong thing, and has been for a year.
Last stated 3 months ago
3 Sept 2026
DR
Dax Raad — holds since 2026-09-03 — tap for who they are
same subject or similar wording a cloud: claims about one subject, named for it bar: when it was last stated, on a scale from 2015 to today — full is today a face: someone who holds the claim — tap it for who they are
At the centre
N+1 queries are probably the second most common cause of poor web app performance, after forgotten indexes.
Last stated 28 May 2024 · 2 years ago
Holds Brandur Leach
Read this korrent →
Similar wording
When diagnosing a performance problem, starting with a CPU profile is more useful than checking database queries first.
Last stated 21 Jul 2026 · 4 months ago
Holds Julia Evans
Similar wording
The steady stream of "we had to rewrite the whole thing because it was too slow" engineering blog posts is the proof that deferring performance to hotspot optimization does not work.
Last stated 26 Aug 2026 · 3 months ago
Holds Casey Muratori
Similar wording
Garbage collection is a problem for backends too, not only for embedded code: a collection that lands on an incoming request is a latency spike.
Last stated 20 May 2026 · 6 months ago
Holds Alice Ryhl
Similar wording
Go is no less susceptible to N+1 queries than a metaprogramming-heavy language like Ruby, despite its verbosity.
Last stated 28 May 2024 · 2 years ago
Holds Brandur Leach
Similar wording
Performance work used to mean half a day reading traces before writing a single fix, and language models have collapsed that step to minutes.
Last stated 19 Aug 2026 · 3 months ago
Holds Addy Osmani
Similar wording
The mass adoption of React and single-page-app architecture across nearly all web apps was driven by trend-following rather than technical fit, producing fragile, scripting-dependent software.
Last stated 25 Apr 2026 · 7 months ago
Holds Phil Hagelberg
Similar wording
The programming practices taught as best practice are ruinous for performance and should not be followed.
Last stated 28 Feb 2023 · 4 years ago
Holds Casey Muratori
Similar wording
Bloated, slow software is caused by a lack of engineering care, not by the choice of technology stack.
Last stated 3 Mar 2026 · 9 months ago
Holds Nikita Prokopov
Same subject: developer tools
A coding agent should probably open in your project folder rather than in the process's parent directory.
Last stated 6 Nov 2026 · 2 weeks ago
Holds Scott Hanselman
Same subject: developer tools
A coding AI that integrates only with its own vendor's tools will be very limited compared with one that draws on all the tools you use.
Last stated 16 Mar 2024 · 3 years ago
Holds Quinn Slack
Same subject: developer tools
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 13 May 2026 · 6 months ago
Holds Anders Hejlsberg
Same subject: compilers
A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting.
Last stated 20 May 2026 · 6 months ago
Holds Alice Ryhl
Same subject: compilers
A programming language is not a compiler but an experience: editing, running, debugging and the runtime library all have to fit together as one cycle.
Last stated 13 May 2026 · 6 months ago
Holds Anders Hejlsberg
Same subject: compilers
A speed difference between languages that share the LLVM backend measures the benchmark author, not the languages.
Last stated 22 Mar 2025 · 2 years ago
Holds ThePrimeagen
Same subject: benchmarks
'Everyone gets it wrong sometimes' is a bad argument when assessing track records.
Last stated 2 Aug 2026 · 4 months ago
Holds Adam Kucharski
Same subject: benchmarks
A benchmark result should be reported under a stated budget, or as a curve against test-time compute — never as a single number.
Last stated 26 Jun 2026 · 5 months ago
Holds Noam Brown
Same subject: benchmarks
A benchmark that ranks Claude Code last while it stays first in use is measuring the wrong thing, and has been for a year.
Last stated 3 Sept 2026 · 3 months ago
Holds Dax Raad