Two MoTacon attendees are on the left. The MoTaacon logo is in the center, and to the right a prompt to Get Your Ticket.

Hot take: Software was bad before AI too

04 Aug 2026

Recently I was playing an online game with friends. The game glitched repeatedly, generally full of bugs. "I'm sure it was vibe coded" remarked one player. Thing is, this is the fourth installment of the franchise that has a long history of bugs - long before AI coding. 

This shifting responsibility bugs me. Don't blame 'vide coding' for bad product. Don't excuse bad quality "because it was made with AI." We have a perfectly proven track record of shipping bad quality products long before AI. The real fault will forever lie with the decision makers. The people that decided to use AI, to code with AI, to approve AI code, and ship AI product.

Companies make bad software. People write bad code. The software would have been just as bad if they did not use AI, as quality is a choice made by said companies and people.  By shifting our language we shift responsibility away from the people making these decisions and we fail to hold them accountable. Don't allow companies to shift the blame, to pretend they are not accountable for these decisions. 

Don't blame the screwdriver for the negligence of the craftsperson. 
Shawn Vernier profile image
Shawn Vernier
Quality Engineer
He/Him

The answer to quality is context.

Open To
Work
Write
Teach
Speak
Mentor
CV Reviews
Podcasting
Mentee
Review Conference Proposals
Ady Stokes
Great point. There have always been bugs. They are a fact of software.

Sign in to comment
Explore MoT
Influence, from the other side of the table image
What I learned about influence by becoming a stakeholder
Prompting for Testers image
Unleash the power of generative AI to boost your software testing and day-to-day tech tasks
This Week in Quality image
Debrief the week in Quality via a community radio show hosted by Simon Tomes and members of the community
Subscribe to our newsletter