TL;DR — My last post was about catching drift: the moment my config tool's idea of "valid" silently diverges from the real Pyxel framework. This post is about the other half of the same system — what happens the instant a human hits one of those checks. A safety net has two jobs: it has to catch you, and it has to talk to you when it does. Perfect code chases the first and forgets the second. I dug into ~60 years of error-message research to work out what a net that talks back should actually say, and mapped each finding onto a concrete rule I now hold my own diagnostics to.
The myth I had to give up first
For a long time I treated "write better code" as the goal, as if enough care up front would let me arrive at software that simply didn't go wrong. That belief survives right up until you maintain a tool whose correctness depends on something you don't own. My browser-based configuration tool exists to help scientists write YAML that ESA's Pyxel detector-simulation framework will accept. Pyxel is the source of truth. My copy of that truth can drift, users will make mistakes I can't anticipate, and no amount of cleverness on my side changes either fact.
So I stopped aiming for code that never fails and started building a net that assumes it will. In the drift post I wrote about the catching layers — freshness checks, bounds tests, API introspection, per-file coverage gates. But a net that catches you silently and then hands you a stack trace is only half a net. The half nobody budgets for is the part that speaks.
