DOP 338: The Assembly Line Problem: Why Adding AI to One Step Breaks Everything
Show Notes
#338: Every company adding AI coding tools runs into the same wall. Developers produce more code, but features don’t ship any faster. The bottleneck just slides downstream – to QA, to security, to legal, to whoever comes next in the pipeline. And the team that got faster? They don’t even realize the people upstream could be feeding them more work.
Viktor’s take: the fastest possible setup is one person carrying a feature from idea to production. Not one person doing everything alone – a system designed so nobody waits. Tests run in CI. Deployments happen through Argo CD. Security scanning is automated. There’s a real difference between wiring up a light switch and hiring a butler to flip it for you.
None of this is new. The same thing happened with punch cards, client-server, cloud, Kubernetes. One group adopts the new thing, everyone else says it doesn’t apply to them, and the market eventually forces their hand. Meanwhile, every team in every company says they’d love to change if only the rest of the organization would get on board. Every team says this. So who’s actually blocked?
Episode Transcript
Share and Download
Hosts
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.