An agent built a Tauri desktop application end to end. The pure logic was correct on the first or second attempt. Every defect that mattered sat at a boundary no headless test can reach.
7 min read
A scanned NASA specification, a novel, the memory of a product, and a sealed algorithm. What four controlled rebuilds establish about where AI-assisted reconstruction of legacy systems actually fails.
8 min read
Cheap code lowers the cost of building the replacement. It does not lower the cost of being wrong about the legacy behaviour, and sent messages do not un-send.
4 min read
The behavioural evidence is contested, which is the argument for checking the workflow first. A replacement judged on new capability gets judged on missing capability instead.
5 min read
A restricted replacement justified as an MVP while failing the operational needs of the users required to adopt it. The diagnosis is the removed work, not the feature count.
4 min read
Waters' name for a legacy-replacement roadmap that delivers useful capability while limiting disruption. It answers a different question from an MVP, and the two coexist in one programme.
4 min read
Three patterns that build a thin end-to-end path before breadth. Two of them overlap and the third is a different kind of thing, because it has to keep an incumbent running alongside.
5 min read
Tell us what you're working on and where you need help.