
Good code and good software engineers

Why performant code matters (but gets widely ignored), with Casey Muratori
Topic 14 of 18
Published Aug 26, 2026 · Clip 1:24:31–1:33:54 (9:23)
Casey defines good code as straightforward code that maps closely to what the machine must do, broken into digestible, well-named, minimally redundant pieces that the compiler can reassemble efficiently — arguing well-architected code usually is fast code, with divergence only at extreme optimization. He compares good engineers to baseball positions: utility infielders who fix anything anywhere, and deep specialists who grind out breakthroughs; team-building means hiring for roles. Non-negotiables: understanding how things work down the stack, and not being dogmatic about untested received wisdom — great engineers focus on what demonstrably works in practice.