@ryanlpeterman: My goal was to record a conversation completely free of "AI doomer" takes as a timeline cleanser. For this episode, I i…
Summary
Ryan Peterman interviews Casey Muratori about computer history, software engineering, and programming practices in a podcast episode focused on balanced tech discussion.
View Cached Full Text
Cached at: 09/14/26, 03:39 PM
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 - https://youtu.be/jHLbL1Eg4gM • Spotify - https://open.spotify.com/episode/4ywz6rOWmFardgZ04tuBTs?si=w-toSznlQFCn6qd6S_r1_g… • Apple Podcasts - https://podcasts.apple.com/us/podcast/the-peterman-pod/id1777363835… • Transcript - https://developing.dev/p/casey-muratori-surprises-in-computer…
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 https://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 https://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
@ryanlpeterman: My goal was to record a conversation completely free of “AI doomer” takes as a timeline cleanser. For this episode, I i…
Channel: @ryanlpeterman Source: https://www.youtube.com/watch?v=jHLbL1Eg4gM&feature=youtu.be
Similar Articles
@cmuratori: My appearance on @GergelyOrosz's Pragmatic Engineer podcast is up!
A podcast episode on the Pragmatic Engineer podcast featuring Casey Muratori discussing software performance and the use of AI to assist in learning Assembly.
@kentcdodds: Thrilled to have been able to spend 45 minutes talking with @unclebobmartin about software architecture, AI coding agen…
Kent C. Dodds announces a 45-minute podcast conversation with Robert C. Martin (Uncle Bob) about software architecture, AI coding agents, and product engineering.
@shaneparrish: I did another podcast with @tobi. We ended up kinda just geeking out on AI for hours. The members' cut is out: https://…
Shane Parrish interviews Tobi Lütke on AI agents, decision-making, and the future of work in a new podcast episode, with a members' cut available.
@svlevine: Thanks Ryan for coming by! This was a fun chat.
Sergey Levine discusses humanoid robotics, the Chinese robotics ecosystem, and future predictions in a chat with Ryan Peterman.
@charliermarsh: Talked with @ryanlpeterman about how software engineering is changing! I like the pull quote, which captures a lot of w…
Charlie Marsh and Ryan Peterman discuss the impact of AI writing code on software engineering, arguing that PR review costs remain constant while generation costs are zero, and share experiences building Ruff, emphasizing rapid iteration, authentic marketing, and the importance of performance benchmarking.