Go slow to go fast. It means writing a planning document and coming to agreement on what we're doing before anyone touches code. It means knowing how we'll test the thing before we start building it.
← 10 November 2026The Pragmatic Engineer
Software correctness and programming languages with Sean Allen
Sean argues that software correctness should be built in from the start through strong type systems, models and workload-driven testing, not checked at late quality gates, and that pragmatism about debt and speed matters.
Watch on YouTube ↗Word for word
Do more with Charlie
Analyze any YouTube videoPaste a link — get its key points and best quotes in minutes. 10 videos a day.Paste a YouTube link →Your own podcast feedAdd up to 10 YouTube channels you follow. Charlie reads their new episodes for you.Add your channels →
Free — sign in with your email, no password.