7 posts
Your unit tests check specific inputs. Symbolic execution checks every possible input. Here's how it works, what it costs, and where to start.
Your test suite has 94% coverage and zero failures. A symbolic execution engine finds a crash in your code in under three seconds. The test is not broken. The…
Abstract interpretation lets you prove runtime errors impossible before execution.
Your test suite passes. Your type checker is green. You ship. Two hours later, production throws an on an edge case no one thought to test. Testing finds bugs.…
Cleanroom software engineering promised zero-defect increments through mathematical verification instead of debugging.
The software industry average in the 1980s was 30 to 60 defects per thousand lines of code. IBM's Cleanroom team shipped a 20,000-line compiler increment with…
AutoVerus uses a network of LLM agents to generate Verus correctness proofs for Rust code, automating over 90% of proof obligations through a...
The hardest part of formal verification has never been the verifier. It is writing the proof. Give a senior Rust engineer Verus, the SMT-based verifier from…
Bounded model checkers like Kani and relational model finders like Alloy let you verify properties with ordinary assertions and constraints.
You don't need to learn linear temporal logic to use a model checker. Tools like Kani, CBMC, and Alloy let you verify properties with ordinary assertions and…
Model checking tools like Kani let you verify Rust properties with assertions instead of formal proofs.
You can prove Rust code correct without writing a single proof. The tool that does it is called a model checker, and for Rust the most practical one right now…
N-version programming assumes your implementations agree.
You built an n-version system. Three independent implementations of the same critical function, a voter that picks the majority result, and a warm feeling that…