korrents

A korrentour readingWhat is a 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.

Drawn from what Casey Muratori said

Subjectsoftware performance
What this subject means

software performance Speed as a mark of quality: bloat, boot times, and software that got slower on hardware that got faster.

Interesting
A private bookmark. Not a position, and never counted.

What Casey Muratori actually said

Word for word, with the source under each one. They did not write this page.

  1. Casey Muratori

    Game and engine programmer

    If every uh software engineer knew to watch out for false serial dependency chains, things where they were creating series of dependent operations that could not be optimized away or other sorts of architectural problems like that that cannot be easily fixed, then the world would look more like just wait and optimize the hotspot, right?

    Where this was said

    Watch from 0:35:57 plays here

    ↗Why performant code matters (but gets widely ignored), with Casey Muratoriyoutube.com

    video · 1h 53m · spoken · machine transcript

    All 26 korrents from this recordingthis one is 9th

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

Do you hold this korrent?Do you also believe this?

Sign in to record that you hold this, with a confidence number of your own.

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.

On the map

Loading the map… or open it on its own page

Open the map on its own page →