Tap a claim on the ring to put it at the centre.
← "Optimize it later" would be safe advice only if every engineer…
17 connected korrents · 14 moments from 1 May 2003 to 7 Oct 2026.
Everything filed under software performance
software performance
Everything filed under compilers
compilers
Everything filed under Python
Python
Everything filed under developer tools
developer tools
Everything filed under infrastructure
infrastructure
Everything filed under design
design
Everything filed under product management
product management
Everything filed under documentation
documentation
Everything filed under data centers
data centers 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: "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. "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: Infrastructure optimised for a single model is one architectural breakthrough away from being worthless. — tap to centre the map on it Infrastructure optimised for a single model is one architectural breakthrough away from being worthless. Last stated 11 months ago
12 Nov 2025
SN
Satya Nadella — holds since 2025-11-12 — 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: Every program can be hardened and optimized basically ad infinitum. — tap to centre the map on it Every program can be hardened and optimized basically ad infinitum. Last stated 2 weeks ago
7 Oct 2026
GR
Guillermo Rauch — holds since 2026-10-07 — tap for who they are
Same subject: Premature design, deciding too early what a program should do, is as dangerous as premature optimization; specifications should be allowed to change on the fly. — tap to centre the map on it Premature design, deciding too early what a program should do, is as dangerous as premature optimization; specifications should be allowed to change on the fly. Last stated 23 years ago
1 May 2003
PG
Paul Graham — holds since 2003-05-01 — tap for who they are
Same subject: It is better not to spend time crafting the exact perfect solution until you know it works; getting an early version you can play with in the product is a really good milestone. — tap to centre the map on it It is better not to spend time crafting the exact perfect solution until you know it works; getting an early version you can play with in the product is a really good milestone. Last stated 6 months ago
8 Apr 2026
IS
Ian Silber — holds since 2026-04-08 — tap for who they are
Same subject: Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth. — tap to centre the map on it Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth. Last stated 3 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
Same subject: Traditional performance engineering methods are insufficient for the scale of modern AI datacenters and need new approaches. — tap to centre the map on it Traditional performance engineering methods are insufficient for the scale of modern AI datacenters and need new approaches. Last stated 8 months ago
6 Feb 2026
BG
Brendan Gregg — holds since 2026-02-06 — 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 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: 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 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
"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 Read this korrent →
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
Infrastructure optimised for a single model is one architectural breakthrough away from being worthless.
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
Every program can be hardened and optimized basically ad infinitum.
Holds
Premature design, deciding too early what a program should do, is as dangerous as premature optimization; specifications should be allowed to change on the fly.
Holds
It is better not to spend time crafting the exact perfect solution until you know it works; getting an early version you can play with in the product is a really good milestone.
Holds
Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth.
Holds
Traditional performance engineering methods are insufficient for the scale of modern AI datacenters and need new approaches.
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 developer using AI coding tools remains responsible for reviewing the code they ship.
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 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