The same four-pass check, cold-open, edge-input, break-it, plain-language, that every RAXXO tool passes before I call it finished.
Every RAXXO tool goes through the same four-pass check before I call it done, not a different one each time
Pass one is the cold-open test, opening the tool with zero memory of how I built it
Pass three is the break-it pass, where the goal is failure, not success
Consistency, not cleverness, is what actually keeps five different products from feeling like five different quality levels
Why "It Works" Was Never a Good Enough Bar
614 tests green, no regressions. That is what the guardrail cost in test churn: zero. The problem...
Four dev-tool ideas this week. Four dead, all from the same cause, and it took me embarrassingly long...
A few weeks ago I built a small tool called routeproof. It tests one narrow, annoying thing about MCP...
There's a particular kind of false confidence that comes from a green accessibility report. The CI...
Happy paths should be automated, and that part isn't up for debate. A suite that runs the same core...
I build a security platform. Last night I stopped adding features and did something less fun and more...
