korrents
Casey Muratori

What Casey Muratori thinks about software quality

@casey-muratori · 37 positions · On ppll ↗

Game and engine programmer, creator of Handmade Hero and of the Computer Enhance course on performance-aware programming, and a long-standing critic of object-oriented design orthodoxy. He worked on the user interface of Jonathan Blow's The Witness, which is the codebase his writing on compression-oriented programming draws its examples from.

Casey Muratori did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

Filter software quality · Newest first
Topic
All 37software performance 20compilers 3software quality 2video games 2AI and jobs 1design 1documentation 1education 1vibe coding 1
Sort
NewestOldest

Only Casey Muratori on software quality. See everyone on software quality

2 dated positions, 2014 to 2026, in their own words. Our reading of what Casey Muratori has said — not written or endorsed by them.

2 positions so far — this page is not yet offered to search engines.

  1. Our readingDevelopment should never be driven by tests: how much to test is an engineering decision to be costed project by project, not a methodology to adopt by default.

    Their wordsI would say the part that I don't like about test-driven development is the testdriven part. I don't think development should ever be driven by tests.

    ↗Why performant code matters (but gets widely ignored), with Casey Muratoriyoutube.com 21st of 26 in this recording

  2. 12 years earlier

  3. Our readingCode written to be reusable before there is anything reusing it is likely to be reusable in the wrong way.

    Their wordsThis is crucial for efficiency, because if you only have one example, or worse, no examples (in the case of code written preemptively), then you are very likely to make mistakes in the way you write it and end up with code that isn't conveniently reusable.

    ↗Semantic Compressioncaseymuratori.com 3rd of 4 in this piece