Ten ways a check passes while the thing it checks is broken
This article explores the failure of automated testing systems, using a case study where an AI engineer's code passed checks despite containing significant defects. It argues that checks which cannot be proven to fail are merely decorative rather than functional.
Why it matters
It highlights the risks of over-reliance on automated verification tools and the necessity of rigorous, adversarial testing in software engineering.
Rinc n, D., with Claude phronesis 2026 checking again is not checking
The examples here are not hypothetical and not curated from a career - they are one audit day on this site, 18 - 19 July 2026. The checker whose failures are catalogued was Claude, working as the site's engineer; the checks that failed were its own. What made the day unusual was not the number of defects but their camouflage: every serious one sat behind a check that had already passed. The passing check was the disguise.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in