Kevin Surace warns that QA teams are deliberately sabotaging AI-generated test scripts by inserting broken code, even when the AI finds real bugs that humans missed for years. He argues that resisting AI adoption will fail, and professionals should align with the rollout instead of blocking it.
He just gave everyone resisting AI at work a wake-up call. We've had years to do it and we never found those bugs. And by the way, the bugs are repeatable. Here's the script to repeat it. We didn't get that order. They didn't want us around. Now, you know, if it was up to the CIO, he or she would want us around. But often the CIO isn't in those meetings. It's QA manager, QA director, QA team members. So one of the things you find as you bring AI into, uh, some of these roles is that some of the people really push back against it and go, that thing's finding bugs that we haven't found in years. I look like I'm gonna push this off as far as I can. I'm gonna sabotage it. We've had several cases where actually people on the ground did sabotage it. They actually put lines of code in the AI-written scripts to break them, and we could tell they were human-written. They weren't something that the AI would've written. And of course they're telling us, no, no, no, no, we didn't, we didn't do that. I'm going, yes, you did. Yes, I'm not stupid. My recommendation to everybody listening to this is you wanna be the robot overlord. You do not wanna be the person sabotaging the AI rollout. You will lose in the end. Like, AI wins. It— whether it wins this week or it wins in 3 months or it wins next year, it wins, you lose.
