Skip to content

Formal methods with Hillel Wayne

July 29, 2026 · 1 h 24 min

Show notes

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.

—

Timestamps

00:00 Intro

03:21 The Crossover Project

10:26 What software engineering does better

14:19 What traditional engineering does better

17:06 Formal methods

28:21 TLA+: what it is and demo

35:47 TLA+ at Amazon

36:59 Ways distributed systems break

39:52 Formal methods and systems thinking

45:09 The value of learning math

49:12 What TLA+ is good for and isn’t

51:39 Alloy: a declarative language for software modeling

57:42 Other formal methods tools

1:00:13 Property-based testing

1:04:20 AI and the need for formal verification

1:11:18 Logic for programmers

1:13:24 Hillel’s 2025 prediction on AI’s impact

1: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 [email protected].



Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe

All episodes of The Pragmatic Engineer

Settings

Display

Language

Decides which stations you see first on the home page.

History

Recently played stations and episodes and your latest searches are only stored in this browser.

Notifications

A short notice when a podcast you follow has a new episode. Turn off single podcasts with the bell on their page.

Account

Save favorites – in the app and on the website.

Keyboard shortcuts

/
Open search
Space
Play or pause
← →
In the player: back 15 s, forward 30 s (episodes) · in a row: next tile
↑ ↓
In a row: target within the tile
Home / End
In a row: first or last tile
Esc
Close window or menu
?
This overview
Now playing

Go to station page

Play next

    Add episodes with “Play next” – they play after the current episode.