Tap a claim on the ring to put it at the centre.
← There is no trade-off between well-architected code and fast code: in…
17 connected korrents · 12 moments from 21 Jul 2024 to 23 Sept 2026.
Everything filed under software performance
software performance
Everything filed under compilers
compilers
Everything filed under developer tools
developer tools
Everything filed under Python
Python
Everything filed under design
design
Everything filed under coding agents
coding agents
Everything filed under documentation
documentation
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: 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.
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: As AI makes code cheaper to produce, understanding and architectural design become more valuable. — tap to centre the map on it
As AI makes code cheaper to produce, understanding and architectural design become more valuable.
Last stated 2 years ago
27 Jan 2025
NE
Nelson Elhage — holds since 2025-01-27 — tap for who they are
Same subject: Cheap building will not mean making the same amount of software faster; it will mean making way more software. — tap to centre the map on it
Cheap building will not mean making the same amount of software faster; it will mean making way more software.
Last stated 4 weeks ago
23 Sept 2026
GT
Geoff Teehan — holds since 2026-09-23 — 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: Deep design expertise does not get squeezed out just because code and analysis got faster. — tap to centre the map on it
Deep design expertise does not get squeezed out just because code and analysis got faster.
Last stated 3 months ago
19 Jul 2026
ES
Elizabeth Stone — holds since 2026-07-19 — 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: 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: What trips up newcomers to Rust is not the code but the shape of their data. — tap to centre the map on it
What trips up newcomers to Rust is not the code but the shape of their data.
Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — 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: 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 people manager needs enough technical depth to follow discussions and judge debates without relying on trust, but not the deepest technical expertise on the team. — tap to centre the map on it
A people manager needs enough technical depth to follow discussions and judge debates without relying on trust, but not the deepest technical expertise on the team.
Last stated 2 years ago
21 Jul 2024
BK
Ben Kuhn — holds since 2024-07-21 — 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
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
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 26 Aug 2026 · 2 months ago
Holds Casey Muratori
Read this korrent →
Similar wording
As AI makes code cheaper to produce, understanding and architectural design become more valuable.
Last stated 27 Jan 2025 · 2 years ago
Holds Nelson Elhage
Similar wording
Cheap building will not mean making the same amount of software faster; it will mean making way more software.
Last stated 23 Sept 2026 · 4 weeks ago
Holds Geoff Teehan
Similar wording
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 26 Aug 2026 · 2 months ago
Holds Casey Muratori
Similar wording
Deep design expertise does not get squeezed out just because code and analysis got faster.
Last stated 19 Jul 2026 · 3 months ago
Holds Elizabeth Stone
Similar wording
Most organisations are bottlenecked on ideas, vision and taste rather than on implementation, so making code cheap does not make them productive.
Last stated 26 Aug 2026 · 2 months ago
Holds David Heinemeier Hansson
Similar wording
Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth.
Last stated 15 Jul 2026 · 3 months ago
Holds Dex Horthy
Similar wording
What trips up newcomers to Rust is not the code but the shape of their data.
Last stated 20 May 2026 · 5 months ago
Holds Alice Ryhl
Similar wording
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 26 Aug 2026 · 2 months ago
Holds Casey Muratori
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 · 5 months ago
Holds Anders Hejlsberg
Same subject: developer tools
A developer using AI coding tools remains responsible for reviewing the code they ship.
Last stated 10 Mar 2026 · 7 months ago
Holds Jon Seager
Same subject: developer tools
A people manager needs enough technical depth to follow discussions and judge debates without relying on trust, but not the deepest technical expertise on the team.
Last stated 21 Jul 2024 · 2 years ago
Holds Ben Kuhn
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 · 5 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 · 5 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: Python
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 20 May 2026 · 5 months ago
Holds Alice Ryhl
Same subject: Python
Python is ugly: full of superfluous instructions kept since 1987 for legacy reasons, and its __init__ offends the sensibilities to the core.
Last stated 12 Jul 2025 · a year ago
Holds David Heinemeier Hansson
Same subject: Python
Sharing code between classes via inheritance in Python tends to produce a bad experience.
Last stated 21 Jul 2026 · 3 months ago
Holds Julia Evans