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.

Added to korrents 26 Aug 2026 · How quotes work · Something wrong? Tell us

Related korrents

Our reading — they may agree, disagree or merely touch the same thing. Closest first: a shared subject counts for most, then how near the wording is.

• How data is laid out and how it is accessed are architectural decisions with nothing to do with hot spots, and the difference between two layouts can be enormous. CMCasey Muratori26 Aug 2026similar wording
• "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. CMCasey Muratori26 Aug 2026similar 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. CMCasey Muratori26 Aug 2026similar 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. CMCasey Muratori26 Aug 2026similar wording
• 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. CMCasey Muratori26 Aug 2026similar wording

See this on the map →