By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
The Pragmatic EngineerSoftware correctness and programming languages with Sean Allen
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
Great conversations run long. Their best ideas don't have to.
uListen is free on iPhone, iPad, Android, Chrome, and Claude.
See howEpisode Details
EPISODE INFO
- Released
- November 10, 2026
- Duration
- 1h 25m
- Channel
- The Pragmatic Engineer
- Watch on YouTube
- ▶ Open ↗
EPISODE DESCRIPTION
We do not mention "AI" a single time - even though this happens to be a deep conversation on the biggest challenges of developing with AI. With Sean Allen (seantallen.com), Distinguished Engineer at Antithesis, we dig up the fundamentals that are as important as ever. — *Timestamps:* 00:00 Intro 01:11 Sean’s path into tech 04:45 Joining Antithesis 06:49 OCaml and type systems 12:25 Ada and compiler guarantees 14:28 F# and .NET 18:26 Pony and safe concurrency 27:16 Rethinking garbage collection 31:48 Software correctness 32:51 Testing as a means to an end 35:41 TDD and property-based testing 40:52 Designing testing workloads 49:30 Why quality isn’t a gate 57:44 Testing complex systems 1:00:50 Supply chain security 1:09:57 Side-channel attacks 1:11:54 Confidential computing 1:14:38 Rethinking technical debt 1:20:14 Going slow to go fast
SPEAKERS
Gergely Orosz
hostSoftware engineer and author who hosts The Pragmatic Engineer podcast/newsletter, interviewing engineering leaders and experts.
Sean Allen
guestSoftware correctness and programming-languages expert who has worked on reliability/security topics (e.g., Antithesis and Microsoft Research confidential computing).
EPISODE SUMMARY
In this episode of The Pragmatic Engineer, featuring Gergely Orosz and Sean Allen, Software correctness and programming languages with Sean Allen explores Correctness over testing: languages, workloads, and limits of assurance Sean Allen frames software correctness as upholding expected behavior and invariants, while noting teams often know failure states better than success criteria.
RELATED EPISODES