Tap a claim on the ring to put it at the centre.
← Everyone on a team who makes architectural decisions must understand…
17 connected korrents · 11 moments from 26 Apr 2023 to 31 Aug 2026.
Everything filed under software performance
software performance
Everything filed under compilers
compilers
Everything filed under design
design
Everything filed under Python
Python
Everything filed under coding agents
coding agents
Everything filed under ideas vs execution
ideas vs execution 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: 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. 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: Most organisations are bottlenecked on ideas, vision and taste rather than on implementation, so making code cheap does not make them productive. — tap to centre the map on it Most organisations are bottlenecked on ideas, vision and taste rather than on implementation, so making code cheap does not make them productive. Last stated 2 months ago
26 Aug 2026
DH
David Heinemeier Hansson — holds since 2026-08-26 — tap for who they are
Same subject: The evidence from the largest software companies says programmers should take performance more seriously than they do, not less. — tap to centre the map on it The evidence from the largest software companies says programmers should take performance more seriously than they do, not less. Last stated 3 years ago
26 Apr 2023
CM
Casey Muratori — holds since 2023-04-26 — 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: Hand-optimizing hot spots barely matters any more, because the libraries are already fast and CPUs are extremely good at running bad code quickly; what is left is architecture. — tap to centre the map on it Hand-optimizing hot spots barely matters any more, because the libraries are already fast and CPUs are extremely good at running bad code quickly; what is left is architecture. Last stated 2 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: The code today’s models and agents write is very hard to follow: you get better performance without knowing why, and no way to fix it when it breaks. — tap to centre the map on it The code today’s models and agents write is very hard to follow: you get better performance without knowing why, and no way to fix it when it breaks. Last stated 3 months ago
19 Jul 2026
ES
Elizabeth Stone — holds since 2026-07-19 — tap for who they are
Same subject: Architectural iteration is slow because a design usually has to be built before its quality can be judged. — tap to centre the map on it Architectural iteration is slow because a design usually has to be built before its quality can be judged. Last stated 7 months ago
11 Mar 2026
KD
Kent C. Dodds — holds since 2026-03-11 — tap for who they are
Same subject: There is no trade-off between well-architected code and fast code: in practice, the code that is architected properly is also the code that runs quickly. — tap to centre the map on it There is no trade-off between well-architected code and fast code: in practice, the code that is architected properly is also the code that runs quickly. Last stated 2 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: An abstraction chosen wrongly at the start means a team can never make its software great, however good that team is. — tap to centre the map on it An abstraction chosen wrongly at the start means a team can never make its software great, however good that team is. Last stated a year ago
18 Sept 2025
TL
Tobias Lütke — holds since 2025-09-18 — 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
Same subject: A good tool raises the floor of what people can build without lowering the ceiling, and almost every tool quietly lowers the ceiling. — tap to centre the map on it A good tool raises the floor of what people can build without lowering the ceiling, and almost every tool quietly lowers the ceiling. Last stated a year ago
18 Sept 2025
TL
Tobias Lütke — holds since 2025-09-18 — tap for who they are
Same subject: A new API framework that ignores how existing apps were historically built undermines its own introduction — tap to centre the map on it A new API framework that ignores how existing apps were historically built undermines its own introduction Last stated 2 months ago
31 Aug 2026
CH
Craig Hockenberry — holds since 2026-08-31 — 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 5 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 5 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: A language can keep changing without a Python-2-to-3 break, as long as code written under the old and the new rules can be mixed freely in one program. — tap to centre the map on it A language can keep changing without a Python-2-to-3 break, as long as code written under the old and the new rules can be mixed freely in one program. Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: Python is ugly: full of superfluous instructions kept since 1987 for legacy reasons, and its __init__ offends the sensibilities to the core. — tap to centre the map on it Python is ugly: full of superfluous instructions kept since 1987 for legacy reasons, and its __init__ offends the sensibilities to the core. Last stated a year ago
12 Jul 2025
DH
David Heinemeier Hansson — holds since 2025-07-12 — tap for who they are
Same subject: Sharing code between classes via inheritance in Python tends to produce a bad experience. — tap to centre the map on it Sharing code between classes via inheritance in Python tends to produce a bad experience. Last stated 3 months ago
21 Jul 2026
JE
Julia Evans — holds since 2026-07-21 — tap for who they are
At the centre
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 Read this korrent →
Most organisations are bottlenecked on ideas, vision and taste rather than on implementation, so making code cheap does not make them productive.
Holds
The evidence from the largest software companies says programmers should take performance more seriously than they do, not less.
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
Hand-optimizing hot spots barely matters any more, because the libraries are already fast and CPUs are extremely good at running bad code quickly; what is left is architecture.
Holds
The code today’s models and agents write is very hard to follow: you get better performance without knowing why, and no way to fix it when it breaks.
Holds
Architectural iteration is slow because a design usually has to be built before its quality can be judged.
Holds
There is no trade-off between well-architected code and fast code: in practice, the code that is architected properly is also the code that runs quickly.
Holds
An abstraction chosen wrongly at the start means a team can never make its software great, however good that team is.
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
A good tool raises the floor of what people can build without lowering the ceiling, and almost every tool quietly lowers the ceiling.
Holds
A new API framework that ignores how existing apps were historically built undermines its own introduction
Holds
A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting.
Holds
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.
Holds
A speed difference between languages that share the LLVM backend measures the benchmark author, not the languages.
Holds
A language can keep changing without a Python-2-to-3 break, as long as code written under the old and the new rules can be mixed freely in one program.
Holds
Python is ugly: full of superfluous instructions kept since 1987 for legacy reasons, and its __init__ offends the sensibilities to the core.
Holds
Sharing code between classes via inheritance in Python tends to produce a bad experience.
Holds