Systems | Development | Analytics | API | Testing

Are we really in the “future of AI,” or are we just learning how to coexist with it? On this episode of Test Case Scenario, we explore: Why critical thinking and clear expectations make AI a tool, not a threat. How understanding its strengths—and its limits—keeps it a net positive. The gradual evolution of AI’s role in productivity, creativity, and problem-solving. The key to success? Making AI work for what it does best.

Are we stuck in a cycle of quick fixes and passing the buck? Tech problems today feel eerily familiar, just on a faster timeline—two-week sprints instead of nine-month cycles. Yet, management keeps hunting for the elusive silver bullet, often leaving the cleanup for the next in line. Is the short tenure of tech roles fueling this carousel of deferred accountability? On this episode of Test Case Scenario, we explore why real innovation requires more than just quick fixes and flashy solutions. Let’s break the cycle.

AI promises efficiency, but are we implementing it the right way? @Marcus Merrell shares what’s critical to track AI usage and its impact: “Here’s the prompt I used to get this tool, and here are the changes I made to make it work.” This kind of transparency is non-negotiable. Start small with a group of mixed experience levels to uncover both benefits and risks before scaling. If AI adds overhead without solving core issues, is it truly worth the investment?

AI tools like Copilot and ChatGPT promised to revolutionize development workflows, but are they delivering or just creating new headaches? The stats speak volumes: 92% of developers say AI increases the blast radius of bad code 67% are spending more time debugging AI-generated code 59% face deployment errors at least half the time when using AI tools So, are we making strides toward innovation or spinning in circles of hype? @Marcus Merrell put it best: “This stuff was supposed to already start paying off by now. So why isn’t it working?”

AI was supposed to be the game-changer for developer productivity, but reality isn’t living up to the hype. GPT-4 took 50x the resources of GPT-3.5, yet the improvement? Barely noticeable. AI-generated code isn’t saving time—it’s creating more debugging, security headaches, and compliance risks. The real issue? It’s not the AI—it’s how we’re using it. AI isn’t freeing up developers for innovation—it’s adding more noise. So, what’s the fix? Catch the full conversation on the latest Test Case Scenario.

AI is reshaping development, but is it meeting expectations? In this episode of Test Case Scenario, Jason Baum and Marcus Merrell explore the evolving role of AI in software development, drawing insights from recent industry reports. They discuss whether AI tools are living up to their promise of reducing burnout and boosting productivity while examining the complexities of debugging, security risks, and governance gaps.

When teams use different programming languages, code becomes territorial. Your code. My code. Your problem. My problem. But when teams align on a single language, those barriers disappear. Suddenly, collaboration is effortless. Debugging isn’t someone else’s job—it’s everyone’s. As Selenium developers, every feature has to work across five languages. AI helps bridge the gap, but the real game-changer? A shared language that makes moving across the codebase seamless.

AI is being treated as a shortcut for quality. Is that a dangerous gamble? There are a few industry-wide experiments happening right now: Developers are being pushed to own quality, but without dedicated testers, gaps are forming. AI is being used as a crutch for testing, but can it actually replace critical thinking? The real risk? We won’t know how badly this approach fails until it’s too late.

AI isn’t a shortcut to perfect testing. It won’t magically fix your processes or write flawless code. But if used right, it will push testers and developers to think more critically. Instead of asking if AI should be part of testing, the real question is how to make it a true collaborator. That means: Using AI to highlight gaps, not blindly trusting its output Treating it as a thought partner, not an automation machine.

AI isn’t replacing testers—it’s becoming an extension of how they think. Here’s how @Maaret Pyhäjärvi sees it: Applications make us more creative, acting as an “external imagination.” Testers do the same for developers—when devs anticipate tester feedback, their testing improves. AI, when used right, serves a similar role: it challenges us to refine and rethink, not just automate. The real power of AI in testing?Doing the work for usPushing us to think better.

AI is changing the way developers and writers work, but not always in the ways we expected. Here’s what’s really happening in 2025: Developers are now spending more time reviewing AI-generated code than writing it. Faster isn’t always better. Writers who used to rely on peer feedback are getting instant AI edits—but at the cost of real collaboration. AI is a powerful tool, but it’s shifting roles instead of eliminating work. The question isn’t if you use AI, it’s how you integrate it.

Is your testing strategy ready for 2025? In this episode of Test Case Scenario, Jason Baum is joined by Maaret Pyhäjärvi, Principal Test Consultant at CGI, along with Diego Molina and Titus Fortner from Sauce Labs, to discuss the evolving landscape of quality assurance and business resilience. The panel delivers insights into the biggest challenges and opportunities for testing teams in 2025, from AI-assisted automation to the growing importance of accessibility testing.

When it comes to AI, we’re focused on the wrong problems. On Test Case Scenario, we discuss the real challenges AI faces in software development: AI can churn out code, sure—but when it comes to maintenance, it’s dead weight. Collaboration over replacement: @Titus Fortner shares why AI isn’t your star coder—it’s your intern, and it needs constant babysitting. The real bottleneck? Writing code isn’t the hard part. It’s building tools that help teams actually understand and sustain their work.

The real obstacle to AI revolutionizing development? Us. Are we bold enough to rebuild processes and make AI a true collaborator? Can we ditch the fantasy of "one tool to rule them all" and embrace smarter, leaner AI teamwork? The future of testing—and AI—demands a total shift in mindset. Are you ready to rewrite the rules? Catch the latest episode of Test Case Scenario to see what’s next.

AI tools promise to revolutionize everything, but are they making us smarter or lazier? Here are the questions I still have about the real impact of AI in development. Are teams using AI to augment their work or replace themselves entirely? Process and social change are a no-brainer, but are we keeping up? Are we adapting or coasting? And the big question: As AI gets smarter, are we dumbing ourselves down, losing our grip on what it means to understand?

AI was seen as a potential means to revolutionize developer productivity, but the 2024 DORA report tells a different story. Here’s the reality developers are facing: Tech debt and documentation remain massive blockers, and AI tools aren’t fixing them. Endless meetings leave no time to code, and AI can’t clear your calendar. AI tools? Useful but unreliable, like a junior dev that needs constant oversight.

Are AI tools really helping developers, or are they creating more problems than they solve? In this episode of Test Case Scenario, Jason Baum, Marcus Merrel, and Evelyn Coleman are joined by Titus Fortner, Senior Solutions Architect at Sauce Labs, to unpack the surprising findings from the latest DORA report. Together, they dive into the unexpected decline in productivity following AI adoption and discuss the challenges developers face in balancing automation, innovation, and collaboration.

AI was hyped as the big solution to developer productivity, but the 2024 DORA report paints a different picture. Here’s what’s holding teams back: Developers don’t need help writing code—they need time to write it. AI isn’t clearing their calendars of endless meetings. Tech debt and documentation remain roadblocks, and AI tools aren’t solving them. AI can assist, but it often acts like a junior dev—adding more work instead of reducing it.