Exploring AI-first development, coding guardrails, and the architecture of disposability.
Meta's Infer uses abstract interpretation and bi-abduction to find null dereferences, memory leaks, and race conditions by reasoning about code structure,...
Meta has shipped over 100,000 bug fixes that were caught by a static analyzer before the code ever reached a user. The tool is called Infer, it is open source,…
Abstract interpretation over-approximates every possible program state.
Static analysis cannot prove an airplane will not crash. It can prove that your altimeter control loop will never divide by zero, will never index out of…
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.…
CHERI's hybrid ABI lets you port C code to capability hardware incrementally.
You have a C codebase that is too large to rewrite in Rust and too critical to leave exposed to buffer overflows. CHERI capability hardware promises to catch…
Memory safety at the hardware level has been possible since the 1970s.
Seventy percent of CVEs are memory safety bugs. Buffer overflows, use-after-free, double frees. The kind of vulnerabilities that let an attacker pivot from a…
Containers are overkill for isolating a single C library.
A single null pointer dereference inside a C library can bring down your entire application. If that library parses user input, decompresses images, or handles…
ARM Memory Tagging Extension and GWP-ASan make production memory safety detection possible on modern mobile devices.
Your phone can detect memory corruption in production. Not with the full instrumentation you run in CI, and not on every allocation. But the hardware in your…
CHERI is a hardware extension that turns every pointer into a bounded capability.
Buffer overflows have been on the CWE Top 25 for twenty years. We have stack canaries, ASLR, DEP, control-flow integrity, and memory-safe languages, yet they…
Cleanroom verification requires generating and discharging proof obligations.
Cleanroom software engineering demands that you prove your code correct before you compile it. That sounds noble until you spend three hours writing loop…
Cleanroom software engineering cuts defect rates by 100×, but full adoption requires separate test teams and formal proofs.
Cleanroom software engineering delivers 0.1 defects per thousand lines of code. The industry average is 10 to 50. The catch is that full Cleanroom requires you…