Free Daily Podcast Summary
The Pragmatic Engineer: Daily Summaries Delivered
by Gergely Orosz
Software engineering at Big Tech and startups, from the inside. Deepdives with experienced engineers and tech professionals who share their hard-earned lessons, interesting stories and advice they have on building software. Especially relevant for software engineers and engineering leaders: useful for those working in tech.
Latest Episodes
The most recent episodes — sign up to get AI-powered summaries of each one.
- 3 days ago1h 35m
AI Skills with Matt Pocock
Brought to You By:• turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable• Linear – the product development system for teams and agents• WorkOS – everything you need to make your app enterprise ready.—Why is the “grill-me” skill so popular, and why does its creator swear by the importance of software fundamentals? Matt Pocock created this widely-used skill – and many others – alongside being an educator, content creator, and engineer. His latest course is AI Hero, and he previously created the Total TypeScript course that generated more than $2.5 million in sales.In this episode, Matt and I discuss his unconventional path from working as a voice teacher to becoming a developer and going all-in on technical education. He reveals how communication skills helped him break into tech, why he took an unusual three-days-a-week contract at Vercel, and how he built Total TypeScript through workshops, courses, and a lot of free content.We also explore “strategic coding,” and how he uses skills like “grill me” and “wayfinder” to plan, delegate, and course-correct with AI agents. Matt explains his “day shift” and “night shift” approach, why splitting context up can keep agents in their “smart zone,” and how concepts from classic software engineering books can guide agents to do better. In this episode, there’s also local versus cloud workflows, whether agents need TDD, how AI is changing the ways that engineers learn the fundamentals, and why humans are still essential in teaching.Timestamps00:00 Intro05:48 How Matt got into tech10:14 How Matt got into open source12:58 Joining Vercel18:39 Total TypeScript23:21 AI’s impact on technical education30:32 Building reusable skills for AI coding agents40:46 The “smart zone” vs the “dumb zone”45:02 The wayfinder skill47:52 Why agents excel at software engineering50:54 “Leading words”1:01:10 Learning the fundamentals1:09:17 Local vs. cloud agents1:12:36 Planning vs. course-correcting1:18:13 TDD and agents1:23:06 Living in the UK1:24:21 Teaching: the human part1:28:36 Advice for junior engineers1:31:07 Gardeners and great engineers1:34:01 Book recommendation—The Pragmatic Engineer deepdives relevant for this episode:• What is "loop engineering?"• The Philosophy of Software Design – with John Ousterhout• Context engineering with Dex Horthy• Are AI agents actually slowing us down?• The AI Engineering Stack• How Codex is built• How Claude Code is built• How Uber uses AI for development: inside look—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
- 1 weeks ago1h 13m
Building Codex with Tibo Sottiaux
Brought to You By:• turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.• Entire – Git hosting, rebuilt for the agentic era. Every agent session, prompt and tool calls: stored in your repo.—Tibo Sottiaux is one of the engineers who created Codex, and today, he heads up the Core Products & Platform org at OpenAI which also includes Codex. He’s also one of the most public faces of Codex due to his frequent – and generous – usage reset announcements, like this one yesterday.In this episode of the Pragmatic Engineer Podcast, Tibo and I discuss how Codex was built and continues to be iterated upon. We explore why the Codex CLI is written in Rust and was released as open source, how the harness and models have evolved, and why Codex supports models from multiple providers.Tibo also shares details about how the OpenAI team uses Codex throughout the software development lifecycle, including code reviews, maintenance, and system rearchitecture. We look into how AI is lowering the cost of changing code – and some interesting side effects of this – the merger of ChatGPT and Codex, and also how Tibo uses the tools in his own work.—Timestamps00:00 Intro07:21 Working at Google12:41 What drew Tibo to OpenAI15:19 The early days of Codex18:20 Why Codex was built in Rust21:15 Why Codex is open source25:50 Codex plays nice with other models: why?32:09 How the harness works36:44 Harness and model improvements41:19 The SDLC behind Codex46:39 Code reviews at Codex52:09 Maintenance and architecture56:43 How AI tools expand what engineers can do1:02:30 The Merge: ChatGPT + Codex1:07:16 How Tibo uses Codex and ChatGPT1:10:44 Advice for engineers who want to work in AI—The Pragmatic Engineer deepdives relevant for this episode:• How Codex is built• How Claude Code is built• How Cursor was built• What is "loop engineering?”• How Uber uses AI for development: inside look• Why Ramp built its own in-house coding agent, Inspect• “I ship code I don’t read”: with Peter Steinberger, the creator of OpenClaw—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
- 3 weeks ago1h 52m
Why performant code matters (but gets widely ignored), with Casey Muratori
Brought to You By:• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.• Sentry – application monitoring software considered “not bad” by millions of developers.• turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.—There can be few people around who care about software performance more than today’s pod guest, Casey Muratori. He’s a programmer and videogame developer, founder of Molly Rocket, and creator of Handmade Hero – a long-running series about building a game from scratch. He also evangelizes about performance on his Substack, Computer, Enhance.We got to know each other about three years ago, first via messages, including this one from Casey:“Why does the industry zeitgeist place so little emphasis on software performance when there seems to be overwhelming evidence that performance is critical to their bottom line?Like you, I run a Substack for professional programmers, but I focus exclusively on software performance. Although we are quite large by Substack standards, so a certain subset of programmers must believe performance is important, I nonetheless hear lots of dismissive excuses when I post on social media. This happens so frequently, I devoted an entire article to cataloging the extensive pro-performance evidence we already have from the world's leading software companies: Performance Excuses Debunked.Strangely, nobody has a rebuttal to why performance is important. When I point people to this, they actually tend to agree. But the prevailing attitude nonetheless stays the same.”I’m delighted we finally have Casey on the podcast because it’s overdue! In this episode, we discuss why software performance matters, why it’s overlooked, and how developers can get better at writing performant code. We explore why performance should be considered during design, the value of learning to read assembly & understanding how CPUs work, Casey’s critique of ‘clean code’, and why he believes testing shouldn't drive software design.We touch on how videogame development has changed, and influential game engines. Casey also tells us why he prefers to write code by hand, not with AI, and more.—Timestamps00:00 Intro05:17 Games at Microsoft12:52 Building games16:00 Why performance matters27:12 Why you should learn to read assembly30:36 Designing for optimization42:51 How to get better at writing performant software49:04 Understanding how the CPU works55:53 Building games then and now1:05:56 How game engines changed building games1:10:48 Why new games compete with old games1:13:25 GTA 6: why is it taking so long?1:16:59 Casey’s critique of clean code1:21:48 Casey’s take on TDD1:24:30 What is good code?1:27:32 What makes a good software engineer?1:33:56 Why Casey doesn’t code with AI1:39:01 AI’s impact on the game industry1:44:43 AI and burnout1:50:21 Why you should read papers—The Pragmatic Engineer deepdives relevant for this episode:•Pushing software engineering limits with “napkin math” with Simon Eskildsen •How Games Typically Get Built: prototyping, game engines, and a different type of QA•Game Development Basics: deepdive on how game studios differ from standard software teams•Inside Linear's Engineering Culture: building a performant product with a tiny team•Building a best-selling game with a tiny team – with Jonas Tyroller. A two-person team buil
- Aug 19, 20261h 31m
From Chrome DevTools to AI Engineering, with Addy Osmani
Brought to You By:• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.• Google Cloud Run – run your code and host LLMs directly on top of Google’s scalable infrastructure, without having to worry about managing infra.• Sentry – application monitoring software considered “not bad” by millions of developers—Addy Osmani spent more than 14 years at Google, working on Chrome, DevTools, Core Web Vitals, and most recently, AI developer experience.If you've ever opened Chrome DevTools, or optimized a page for Core Web Vitals, you’ve used software built by Addy Osmani. In this episode, I sit down with Addy and we talk about his path from building a web browser aged just 16 to becoming a director at Google. We discuss what he learned from building tools for millions of developers, Google’s engineering culture, and why he continued doing hands-on coding work as a manager. We also get into how he works with AI agents today, the risks of ‘cognitive surrender,’ his approach to ‘loop engineering,’ and why it’s good to develop skills in product management, go-to-market, and other areas.—Timestamps00:00 Intro02:50 Addy’s current workflow05:11 Addy’s path into tech15:04 Addy’s work on jQuery16:44 TodoMVC21:44 Getting hired at Google and working on Chrome27:17 Building dev tools40:15 Core Web Vitals45:42 Google’s engineering culture51:03 Addy’s career trajectory at Google57:55 The director role at Google1:01:40 Cognitive debt and cognitive surrender1:03:03 Working with agents1:05:52 Loop engineering1:12:55 The changing role of the software engineer1:18:15 How Addy uses AI in writing1:27:40 What’s next for Addy1:28:47 Career advice—The Pragmatic Engineer deepdives relevant for this episode:• What is loop engineering?• Inside Google’s engineering culture• How AI-assisted coding will change software engineering: hard truths• Are AI agents actually slowing us down?• How Claude Code is built• How Codex is built• From IDEs to AI Agents with Steve Yegge• Google’s engineering culture: the podcast—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
- Aug 12, 20261h 25m
Stop being skeptical about AI for development with Charity Majors
Brought to You By:• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.• WorkOS – everything you need to make your app enterprise ready.• Buildkite – CI software built to absorb whatever your coding agents throw at the build queue—In 2025, it was rational to be skeptical about AI, but in 2026 it’s clear that AI is changing all of the industry, and there’s less and less place for skepticism. This take is from one of my favorite voices in software reliability and observability: Charity Majors, CTO and cofounder of Honeycomb, co-author of Observability Engineering. (Note: the second edition of Observability Engineering is out, and it’s pretty much a full rewrite of the book, I recommend grabbing it if you’re building reliable systems)In this episode, I sat down with Charity to discuss how her thinking on AI has evolved, why she believes it is becoming a foundational part of software engineering, and what that means for how teams build, review, and ship software.We explore how AI is changing the economics of code generation, why reliability and verification are increasingly the bottlenecks, and why the rise of non-deterministic systems requires more engineering discipline. Charity shares her views on code reviews, observability, DevOps, leadership, and why both AI skeptics and enthusiasts are getting important things right.—Timestamps00:00 Intro02:56 How Parse led to Honeycomb06:00 The limits of individual productivity metrics09:08 How Charity’s perspective on AI has evolved13:50 Rewriting code vs. editing code19:20 Production as a stage of development22:14 Code reviews26:56 Non-deterministic systems31:11 Sensible uses of AI37:41 The two AI camps44:40 Why AI works so well for building software49:42 DevOps55:13 Modern observability1:00:40 Handling context overload1:01:56 What’s new in Observability Engineering’s 2nd edition1:07:45 What effective leadership looks like1:10:25 Engineering management: what is changing?1:16:31 Junior engineers1:18:01 AI fatigue1:21:39 Book recommendations—The Pragmatic Engineer deepdives relevant for this episode:• Shipping to production• Deepdive: How 10 tech companies choose the next generation of dev tools• Why is Meta destroying its engineering organization?• When AI writes almost all code, what happens to software engineering?• Are AI agents actually slowing us down?• Observability: the present and future, with Charity Majors• The third golden age of software engineering – thanks to AI, with Grady Booch—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
- Jul 29, 20261h 23m
Formal methods with Hillel Wayne
Brought to You By:• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.• turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.• WorkOS – everything you need to make your app enterprise ready.—There’s a popular theory that AI will finally make formal verification mainstream because mathematical proof of correctness will be needed when machines write most or all of the code. But will this happen? Today, I’m talking with one of the best people to tackle the prediction. Hillel Wayne is a formal methods consultant, educator, and author, who’s deeply interested in software history. In this episode of Pragmatic Engineer podcast, I sit down with Hillel to compare software engineering with traditional engineering, discuss where formal methods fit into modern software development, and we explore why they are essential for some of the world's most complex systems. We cover the formal specification language, TLA+, walk through several formal verification tools, examine why distributed systems are so difficult to reason about, and look into whether AI will make formal methods accessible to more engineering teams.—Timestamps00:00 Intro03:21 The Crossover Project10:26 What software engineering does better14:19 What traditional engineering does better17:06 Formal methods28:21 TLA+: what it is and demo35:47 TLA+ at Amazon36:59 Ways distributed systems break39:52 Formal methods and systems thinking45:09 The value of learning math49:12 What TLA+ is good for and isn’t51:39 Alloy: a declarative language for software modeling57:42 Other formal methods tools1:00:13 Property-based testing1:04:20 AI and the need for formal verification1:11:18 Logic for programmers1:13:24 Hillel’s 2025 prediction on AI’s impact1:20:19 Book recommendation—The Pragmatic Engineer deepdives relevant for this episode:• How to debug large, distributed systems: Antithesis• How AWS S3 is built• Paying down tech debt• How Big Tech does quality assurance (QA)• Bug management that works• Resiliency in distributed systems—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
- Jul 15, 20261h 32m
Context engineering with Dex Horthy
Brought to You By:• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.• Buildkite – CI software built to absorb whatever your coding agents throw at the build queue.• Sentry – application monitoring software considered “not bad” by millions of developers.—Knowing how LLM contexts work and how to work around context limitations – aka “context engineering” – is becoming more important for software engineers working with LLMs. Let’s look into what works and what doesn’t, today.In this episode of The Pragmatic Engineer podcast, I sit down with the CEO and cofounder of HumanLayer, Dex Horthy, who coined the term “context engineering”. We discuss the ideas behind this context engineering, harness engineering, loop engineering, software factories, why his approach to AI-assisted software development has evolved, and how HumanLayer is helping engineering teams automate more of the software development lifecycle without sacrificing code quality.—Timestamps00:00 Intro 01:33 Dex’s path into tech03:34 Early work in platform engineering05:28 Replicated11:24 Metalytics12:36 12-factor agents18:27 Context engineering23:38 Harness engineering26:11 Context overload30:45 Loop engineering44:34 Software factories before and after AI50:33 Automation limits55:18 Three options for automating59:00 RPI framework1:04:16 Intentional compaction1:11:48 Token harder vs. token smarter1:16:44 AI slop1:19:15 HumanLayer1:29:09 Book recommendation—The Pragmatic Engineer deepdives relevant for this episode:• How Uber uses AI for development: inside look• Are AI agents actually slowing us down?• AI Tooling for Software Engineers in 2026• Vibe Coding as a software engineer• How Claude Code is built• AI Engineering in the real world• The AI Engineering Stack• How AI-assisted coding will change software engineering: hard truths• The creator of OpenClaw: "I ship code I don't read"—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
- Jul 8, 20261h 18m
The Pragmatic Engineer AMA
Brought to You By:• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.—In this special “ask me anything” episode of Pragmatic Engineer podcast, I am in the hot seat facing questions sent in by subscribers that are read out by guest Volodymyr Giginiak, CTO and cofounder of Wordsmith AI, a legal tech startup (note: I’m an investor).I tackle your questions on the software industry, AI, hiring, engineering organizations, career growth, the business model of the Pragmatic Engineer, and more. We also discuss where software engineering is headed, and I offer advice on some specific situations. Thanks to everyone who sent questions!—Timestamps00:00 Intro01:56 From Uber to writing09:22 AI-native SDLC14:00 AI and hiring19:06 Engineers currently thriving22:18 Junior roles24:44 Meta’s war mode27:54 AI at Big Tech vs. startups36:46 Tech debt41:36 Types of engineering managers44:40 Measuring AI productivity48:30 The value of CS degrees50:53 AI at Pragmatic Engineer56:09 Future-proofing your career1:01:36 The EU job market1:03:55 Making money as a creator1:08:20 What’s next for The Pragmatic Engineer1:09:27 Bunq and Pollen1:13:38 Spotting trends1:14:33 Book updates1:15:20 Favorite books & tech products1:17:13 What won’t change in engineering—The Pragmatic Engineer deepdives relevant for this episode:• State of the software engineering job market in 2026• The impact of AI on software engineers in 2026: key trends. • How 10 tech companies choose the next generation of dev tools • The reality of tech interviews—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
Get The Pragmatic Engineer summaries in your inbox
Free AI-powered daily recaps. Key takeaways, quotes, and mentions — in a 5-minute read.
Get Free Summaries →Free forever for up to 3 podcasts. No credit card required.
You Might Also Like
Listeners also like.
Practical AI
Discussions on practical applications of AI, machine learning, and related technologies for professionals, students, and enthusiasts.
Lenny's Podcast: Product | Career | Growth
Conversations with top product and growth leaders offering practical strategies for building, launching, and scaling successful products.
Everyday AI Podcast – An AI and ChatGPT Podcast
Practical AI and ChatGPT tips for professionals to improve productivity and grow their careers.
Latent Space: The AI Engineer Podcast
Explores AI engineering breakthroughs in foundation models, code generation, and AI agents through interviews with researchers and developers.
The Digital Executive
A daily tech podcast exploring emerging technologies through interviews with Silicon Valley CEOs, influencers, and celebrities.
Dive Club 🤿
Interviews with leading designers exploring craft, storytelling, tools, and design in startups and engineering.
Syntax - Tasty Web Development Treats
Two full stack developers discuss JavaScript frameworks, CSS updates, and web tooling advancements.
Deep Questions with Cal Newport
Answers reader questions on focus, productivity, and living meaningfully in a distracted digital world.
How I AI
A practical guide to using AI tools in work and life, featuring guests who share specific, actionable techniques and workflows.
"The Cognitive Revolution"
Interviews with AI developers and researchers exploring the transformative impact of artificial intelligence on society and technology.
Technology Now
A podcast exploring cutting-edge technology trends and innovations through interviews with industry leaders and HPE experts.
Expert Intelligence with Paul Estes
Examines how AI and human expertise are reshaping work, freelancing, and workplace dynamics through expert conversations.
About The Pragmatic Engineer
Software engineering at Big Tech and startups, from the inside. Deepdives with experienced engineers and tech professionals who share their hard-earned lessons, interesting stories and advice they have on building software. Especially relevant for software engineers and engineering leaders: useful for those working in tech.
Customized Recaps
AI-powered recaps with compact key takeaways, quotes, and insights.
Straight to Your Inbox
Get key takeaways from The Pragmatic Engineer in a 5-minute read.
Save Hours Every Week
Stay current on your favorite podcasts without falling behind.
Frequently Asked Questions
What is Podzilla's The Pragmatic Engineer daily summary?
It's a free AI-powered email that summarizes new episodes of The Pragmatic Engineer as soon as they're published. You get the key takeaways, notable quotes, and links & mentions — all in a quick read.
How does the The Pragmatic Engineer podcast summary work?
When a new episode drops, our AI transcribes and analyzes it, then generates a personalized summary tailored to your interests and profession. It's delivered to your inbox every morning.
Is this an official The Pragmatic Engineer product?
No. Podzilla is an independent service that summarizes publicly available podcast content. We're not affiliated with or endorsed by Gergely Orosz.
Can I get summaries of other podcasts too?
Absolutely! The free plan covers up to 3 podcasts. Upgrade to Pro for 15, or Premium for 50. Browse our full catalog at /podcasts.
How often does The Pragmatic Engineer release new episodes?
The Pragmatic Engineer publishes weekly. Our AI generates a summary within hours of each new episode.
What topics does The Pragmatic Engineer cover?
The Pragmatic Engineer covers topics including News, Technology. Our AI identifies the specific themes in each episode and highlights what matters most to you.
Start getting The Pragmatic Engineer summaries tomorrow morning.
Free forever for up to 3 podcasts. No credit card required.
Free forever for up to 3 podcasts. No credit card required.