My goal was to record a conversation completely free of "AI doomer" takes as a timeline cleanser. For this episode, I interviewed Casey Muratori (@cmuratori) who is a video game developer and programming creator also known for his talks about the history of computing. In this episode: • Surprising findings in computer history • Where bad code comes from • The only unbreakable law in software engineering • His career in the video game industry • Why you should read technical papers Where to watch: • YouTube - youtu.be/jHLbL1Eg4gM • Spotify - open.spotify.com/episode/4yw… • Apple Podcasts - podcasts.apple.com/us/podcas… • Transcript - developing.dev/p/casey-murat… Thank you to the sponsors of this episode for supporting my work: • Jira by Atlassian: Get more work done with your favorite agents and models all in one place, check them out at jira.dev/ • WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at workos.com/ Chapters: 00:00 Intro 01:08 Digging into computer science history 04:08 What shocked him 16:23 Dijkstra was depressed 26:17 The personal side of goto considered harmful 35:09 The anatomy of a 35 year mistake 50:12 Clean code horrible performance 58:33 How to write high performance code 01:01:18 Where bad code comes from 01:06:37 Why design docs before code is a bad idea 01:09:20 The only unbreakable law in software engineering 01:15:57 How he got into programming 01:21:16 Why he didnt work in big tech 01:30:44 Should you work at a startup early on 01:34:52 What video game engineering is like 01:39:57 Why preventing recursion is reasonable 01:43:24 Is vibe coding bad for the industry 01:50:17 Technical reading recommendation 01:54:27 Advice for his younger self 01:56:54 Outro