DOP 341: AI Widened the Highway but Nobody Rebuilt the Bridge

Episode 341

Show Notes

#341: Nobody’s arguing about whether you need feature flags in 2026. That debate ended years ago. But the code flowing through those flags? That’s a different story. AI is writing more of it than ever, review times are climbing, and delivery throughput has actually declined. Trevor Stuart, co-founder of Split.io and now running Feature Management & Experimentation at Harness, calls it the six-lane highway ending in a two-lane bridge.

The bottleneck didn’t disappear. It moved. Coding got faster, but everything downstream – reviews, security scans, delivery pipelines – stayed the same width. Viktor points out this is the exact same pattern from the early agile days: his team shipped every two weeks, but testing still took six months. Different era, same structural problem.

Feature flags are part of the fix, but not the way most people use them. Teams are now stuffing prompts, token limits, and temperature settings inside feature flag configurations and running A/B tests on AI agents in production. That’s a long way from changing button colors on a marketing page, which is where experimentation started 15 years ago.

The culture problem is harder than the tooling problem. Trevor has watched teams run one experiment, see it fail, and quit experimenting entirely. The fear of admitting failure kills more experimentation programs than bad data ever will. Meanwhile, the companies getting real results – a fast food chain generating millions from kiosk experiments, a global bank driving hundreds of millions in customer acquisition – are the ones treating experimentation as a permanent operating model, not a one-off project.

The conversation also covers Trevor’s path from co-founding Split to running it inside Harness post-acquisition. He stayed – which doesn’t happen as often as you’d think. Harness runs what he calls a ‘startup within a startup’ model, and he breaks down what that actually looks like from the inside, what was hardest to let go of, and why finding your ‘why’ matters more than any exit.

Frequently Asked Questions

Why is AI-generated code not shipping any faster?

Trevor Stuart brings the analogy on DevOps Paradox episode 341 of a six-lane highway ending in a two-lane bridge. Code volume exploded, but throughput went down, because more code means more security vulnerabilities and more review time. Viktor Farcic reads the bottleneck as adoption rather than any particular phase, describing teams putting a new shiny thing into an old ugly box and expecting the same processes to hold.

Are feature flags still worth adopting in 2026?

Trevor Stuart’s answer on DevOps Paradox episode 341 is that most teams already have them, homegrown or from a vendor, and that they became table stakes in software delivery. He contrasts that with conference conversations ten years ago, where people still asked whether a feature flag was just a config file. The question he now hears is how to undo the technical debt all those flags created.

How are feature flags being used with AI?

Trevor Stuart describes on DevOps Paradox episode 341 customers putting prompts, tokens and temperature settings into the JSON configuration attached to a flag treatment. That lets them run prompt tests against real traffic, turning one variant on for five percent of customers and a second variant on for another five. He expects AI configs and AI evals to become normal parts of the delivery pipeline.

Do teams actually remove old feature flags?

Trevor Stuart admits on DevOps Paradox episode 341 that they do not, not as often as they should, and says he has hundreds awaiting removal in his own code. Viktor Farcic presses on why it is hard: deleting a disabled block is simple, but the surrounding code was written around the flag and needs refactoring. Trevor credits coding agents with finally making automated removal workable.

Can a team get experimentation wrong?

Trevor Stuart’s answer on DevOps Paradox episode 341 is that the failure is cultural rather than technical. Teams that run one experiment, watch it fail, and then ship whatever they had planned anyway have left the experimentation mindset entirely. Accepting failure is the hard part, because a failed experiment means admitting an idea did not work, and the value arrives across the next thirty.

Should you test in production?

Trevor Stuart argues yes on DevOps Paradox episode 341, because a pre-production environment never fully mimics production and some features only misbehave under real load. He offers a case where his own team cleared QA, skipped production testing, and shipped something broken. Viktor Farcic sharpens it: production is the only test that really matters, and everything earlier buys confidence to get there.

What is the DevOps Paradox podcast?

DevOps Paradox is a weekly podcast co-hosted by Darin Pope and Viktor Farcic, covering DevOps, platform engineering, and modern software delivery. Episode 341, “AI Widened the Highway but Nobody Rebuilt the Bridge,” brings in Trevor Stuart of Harness on why more generated code has not produced faster delivery, and what feature flags do with prompts. Every episode page carries the audio, the video, and a full transcript.

Topics

Share and Download

Guests

Trevor Stuart

Trevor Stuart

Trevor is the Senior Vice President and General Manager at Harness, where he leads the company’s Feature Management and Experimentation and Software Engineering Insights offerings and works closely on AI platform and AI partnership strategies. He brings a wealth of experience across operations, product management, and startup investing, with a proven track record in both startup and large enterprise environments.

Before joining Harness, Trevor was the President and Co-Founder of Split Software, which was acquired by Harness in 2024. At Split, Trevor played a pivotal role in driving the company’s growth and product innovation. Prior to founding Split, he was responsible for leading product simplification initiatives at RelateIQ, which was acquired by Salesforce.

A passionate advocate for data-driven innovation, Trevor is dedicated to enabling product and engineering teams to scale rapidly through informed, data-centric decision-making. He is also committed to building and nurturing high-performing teams.

Outside of work, Trevor enjoys spending time in Sonoma County California, where he can often be found relaxing with a glass of wine and his dog, Crockett.

Hosts

Viktor Farcic

Viktor Farcic

Viktor Farcic is a member of the Google Developer Experts and Docker Captains groups, and published author.

His big passions are DevOps, Containers, Kubernetes, Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD).

He often speaks at community gatherings and conferences.

He has published DevOps Paradox and Test-Driven Java Development.

His random thoughts and tutorials can be found in his blog The DevOps Toolkit.