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.

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.

• 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. 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
• Performance work used to mean half a day reading traces before writing a single fix, and language models have collapsed that step to minutes. AOAddy Osmani19 Aug 2026similar wording
• 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. ESElizabeth Stone19 Jul 2026similar wording
• Repeated rewrites are the correct answer under fast growth, because a system specified to scale forever would take so long to build that the company would die before it shipped. TPThuan Pham1 Apr 2026similar wording

See this on the map →