
AI Is Shipping Your Blind Spots
I shipped a spec that missed three edge cases a QA engineer would have caught in five minutes. Not buried edge cases. Not obscure branching logic deep in a data model. Surface stuff. The kind of thing that lives at the front of the test plan, the first page of the test run, so obvious in hindsight that explaining it in a retrospective is the most embarrassing part. There was no incident. No postmortem. Just a dev cycle quietly bleeding out through holes that should never have made it past the spec. The QA team's test cases weren't ready yet. That happens in spec-driven development ... teams don't always move in lockstep, and some functions are still prepping when others are already building. I know this. I've been managing that coordination for years across teams on three continents. But knowing the gap existed didn't stop me from walking straight into it. The happy path was solid. The spec covered the main flow perfectly. It just never got the perspective of someone whose entire job i
Continue reading on Dev.to
Opens in a new tab


