normative

Asserts Everywhere Crash on Impossible States

Putting asserts everywhere—both positive space (things that should happen) and negative space (this pointer should never be null)—that crash the program when an impossible state is reached, running in both production and testing, lets you catch errors before they become bugs and pinpoint exactly where things went wrong, as TigerBeetle does with deterministic simulation testing.

normativepending

Speaker

ThePrimeagen

Evidence Quote

“these asserts run both in production and in testing. They're always on... they take deterministic simulation testing and run like 200 years of just random data... and when an assert happens, they're like, here's the input that caused it”

Source

Theprimeagen— Lex Fridman Podcast
Created: 6/13/2026, 3:36:30 AM

Your notes

Loading notes...