Tap a claim on the ring to put it at the centre.
← The programming practices taught as best practice are ruinous for performance and should not be followed.
17 connected korrents · 12 moments from 5 Oct 2017 to 26 Aug 2026.
Everything filed under software performance
software performance
Everything filed under documentation
documentation
Everything filed under software quality
software quality
Everything filed under design
design
Everything filed under JavaScript
JavaScript
Everything filed under coding agents
coding agents
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: The programming practices taught as best practice are ruinous for performance and should not be followed. 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: The specific rules taught as clean code are simply bad programming practices, and they get worse when you apply them together. — tap to centre the map on it The specific rules taught as clean code are simply bad programming practices, and they get worse when you apply them together. Last stated 2 months ago
26 Aug 2026
CM
Casey Muratori — 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: Robert C. Martin's advice makes code worse, because it dismisses every correctness technique that is not unit testing. — tap to centre the map on it Robert C. Martin's advice makes code worse, because it dismisses every correctness technique that is not unit testing. Last stated 9 years ago
5 Oct 2017
HW
Hillel Wayne — holds since 2017-10-05 — tap for who they are
Same subject: No single way of modeling data and methods in code is universally correct; every approach is just a set of trade-offs. — tap to centre the map on it No single way of modeling data and methods in code is universally correct; every approach is just a set of trade-offs. Last stated 5 years ago
8 Feb 2022
PH
Phil Hagelberg — holds since 2022-02-08 — tap for who they are
Same subject: Much of the wisdom programmers pass on to each other is nonsense that nobody ever tested, and refusing to be dogmatic about untested practice is what marks out a good engineer. — tap to centre the map on it Much of the wisdom programmers pass on to each other is nonsense that nobody ever tested, and refusing to be dogmatic about untested practice is what marks out a good engineer. Last stated 2 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — 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: You cannot be best of breed in an ecosystem by telling its developers to write in a different programming language. — tap to centre the map on it You cannot be best of breed in an ecosystem by telling its developers to write in a different programming language. Last stated 5 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — 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: "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
The programming practices taught as best practice are ruinous for performance and should not be followed.
Holds Read this korrent →
The specific rules taught as clean code are simply bad programming practices, and they get worse when you apply them together.
Holds
Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth.
Holds
Robert C. Martin's advice makes code worse, because it dismisses every correctness technique that is not unit testing.
Holds
No single way of modeling data and methods in code is universally correct; every approach is just a set of trade-offs.
Holds
Much of the wisdom programmers pass on to each other is nonsense that nobody ever tested, and refusing to be dogmatic about untested practice is what marks out a good engineer.
Holds
What trips up newcomers to Rust is not the code but the shape of their data.
Holds
You cannot be best of breed in an ecosystem by telling its developers to write in a different programming language.
Holds
Most organisations are bottlenecked on ideas, vision and taste rather than on implementation, so making code cheap does not make them productive.
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