Share from 0:00
0:00
/

Correct by design: the video edition

Edition 016 in 24 minutes: how to trust code your agents write and nobody reads in full.

This is edition 016 as a narrated video. It follows Sean Allen’s public writing on correctness: decide what working means before the code exists, use tools that refuse wrong programs, test whole workloads under failure, and limit what installed packages can do.

Code panes, balances and dates marked “example” or “schematic” are illustrations. The numbers come from the sources below.

The full written edition, with every source: https://www.scalableapps.io/p/correct-by-design-software-correctness

Main sources:

  • CodeRabbit, “Our new report: AI code creates 1.7x more problems”, Dec 2025

  • DORA, “2025 State of AI-assisted Software Development”

  • Google Security Blog, “Eliminating Memory Safety Vulnerabilities at the Source”, Sep 2024

  • Google, “Rust in Android: move fast and fix things”, Nov 2025

  • Mündler et al., “Type-Constrained Code Generation with Language Models”, Apr 2025

  • Jepsen analyses of YugaByte DB 1.1.9, TiDB 2.1.7 and MariaDB Galera Cluster 12.1.2

  • Zhou et al., “FoundationDB: A Distributed Unbundled Transactional Key Value Store”, SIGMOD 2021

  • Charity Majors, “I test in prod”, Increment, Aug 2019

  • William Woodruff, “We should all be using dependency cooldowns”, Nov 2025

  • Andrew Nesbitt, “Package managers need to cool down”, Mar 2026

Discussion about this video

User's avatar

Ready for more?