Why performant code matters (but gets widely ignored), with Casey Muratori
Summary
Casey Moratori argues that most software runs significantly slower than necessary due to a lack of performance awareness. He advocates for understanding theoretical hardware limits and reading assembly to identify true bottlenecks, rather than relying on profiling alone. Moratori contends that "premature optimization" is often misused to justify poor architectural choices, like serial dependency chains, which force costly rewrites later.
Topics discussed
Introduction: Why developers neglect performance
Casey's early career and DEC history
Flight Simulator and Windows gaming origins
WinG, DirectX, and entering the game industry
Casey's work on Halo and current projects
Enterprise software performance neglect
Rising focus on performance and benchmarking
Optimization methodology and learning systems
The value of reading assembly language
Architecture vs. hotspot optimization
Case studies: Linear and Antithesis
AI companies rewriting in Rust for performance
Understanding CPU internals and cache
CPU microarchitecture and optimization limits
Evolution of game engine development
Game industry saturation and old games
Grand Theft Auto 6 as a product replacement
Clean code, testing, and compiler optimizations
Defining a good software engineer
AI coding assistants and craftsmanship
AI impact on jobs and reading research papers
Listen ad-free on Castria