Reader · no content
No body text on file.
Open the original to read the full piece.
Why Testing is Hard and How to Fix it with Will Wilson
Brief
On business and adoption, Ron explained Jane Street began as a customer—engineer Doug Patty ran Antithesis on Aria and the tool found previously unseen bugs—then went on to lead Antithesis’s Series A. Wilson described the sales story as pushing the safety‑vs‑speed frontier: customers either get higher confidence at the same pace or accelerate development while maintaining reliability. He cited AI code generation (LLMs/agent loops) as a major spur: synthesized code increases verification needs, but creates new constraints (fast feedback loops and strong validators) that Antithesis is engineering toward. Finally, Wilson sketched Antithesis’s culture—high‑trust, collaborative design debates, flattened internal titles and deliberate hiring to preserve long tenure—and said those social choices help them iterate, absorb feedback from customers, and pivot (as they recently did) when tooling and market signals changed.
Why it matters
Will Wilson (co-founder & CEO, Antithesis) described FoundationDB’s deterministic-simulation practice: run an entire network of database processes inside a single Linux process with deterministic task scheduling, mocked network/disk, and replayability — an approach he says enabled FoundationDB’s small team (~10 people) to build a production-grade distributed database and to safely delete dependencies like ZooKeeper.
Key details
- Antithesis implements determinism below the OS by providing a deterministic hypervisor that runs unmodified guest OSes/VMs; it deduplicates guest memory pages with copy‑on‑write so many branched executions share RAM, enabling large parallel explorations at near‑native speed — technical claims made by Will Wilson.
- Will framed testing as a basket of techniques: property‑based testing (QuickCheck/Hypothesis style), fuzzing (coverage‑guided evolutionary fuzzers), constraint/solver techniques and ML; he emphasized that coverage‑guided fuzzers use code‑coverage signals to evolve inputs, complementing PBT’s generators and invariants.
- Non‑determinism is the central obstacle for testing large interactive systems: threads, timers and hardware‑level variance explode the observable state space. Will asserted Linux’s behavior is highly chaotic — a one‑bit memory change can yield system‑wide divergence within tens of microseconds — making replay and coverage heuristics fragile.
- Jane Street became both a customer and a lead investor in Antithesis’s Series A after internal engineer Doug Patty applied Antithesis to Aria (Jane Street’s distributed system) and the tool found new, actionable bugs — Ron Minsky recounted Jane Street’s involvement and investment rationale.
- Will argued that Antithesis helps push out the safety‑vs‑speed frontier: teams can choose to be much safer at current velocity or move faster while preserving reliability. He also said AI code generation (LLMs/agents) has made verification more urgent because synthesized code multiplies risk of regressions and subtle correctness failures.