DOP 373: Are Layoffs Really Because of AI?
Is that really because of AI? Or just a really good press release? Layoffs used to mean a company was bleeding cash. Now they show up next to record quarters, and AI gets the credit.
Podcast profile
By Darin Pope & Viktor Farcic
What is DevOps? We will attempt to answer this and many more questions.
Latest episode
45 min
Topics
Software delivery, infrastructure automation, CI/CD, collaboration, and operational practice.
Kubernetes architecture, operations, ecosystems, workloads, and cluster management.
Internal developer platforms, paved roads, self-service infrastructure, and platform teams.
Formats
Detailed technical, architectural, or research-oriented examination.
Interpretation, opinion, debate, review, and analytical discussion.
Audience level
Regularly assumes specialist knowledge and discusses implementation, architecture, protocols, code, or research in depth.
Stay connected
From the feed
Episodes shown — 10 of 25
Is that really because of AI? Or just a really good press release? Layoffs used to mean a company was bleeding cash. Now they show up next to record quarters, and AI gets the credit.
Problem solved, right? A few people never touch it. Most use it like a drive-through window -- type a question, grab the answer, leave. And the ones using it all day for emails assume that makes them good at it. But think about it.
Why would you pay for a CRM when you can vibe code one this weekend? Day one, it looks great. You love it. Then day 30 shows up. Somebody else needs access, a new feature breaks an old one, and you're asking yourself where this thing is even hosted.
Three years ago, manual testers were told to learn automation or find another job. Now the automation engineers are hearing the same thing about AI. Same speech, new audience. Here's the thing. Nobody can test everything.
Ten different ways to calculate sales tax. An agent that switches programming languages in the middle of a request. One team on NodeJS, another on Python, and nobody with a rule about either. So who's supposed to stop that?
Your teammates are faster with AI. More tickets closed, more deployments going out than a year ago. So why can't anybody in the building answer a simple question: are we shipping more value? Jeff's take is that the bottleneck didn't go away, it moved. Code got cheap.
A company with no employees, just a founder and an army of AI agents. Zero headcount. Zero payroll. Then the AI CMO hallucinates a marketing campaign and somebody has to catch it. Viktor runs the numbers on his own one-person operation. He can review maybe five things a night.
Maybe you ran it a dozen times. Every one of those pulled down a dependency tree you have never read, from a registry that spent years in maintenance mode, and then executed whatever preinstall and postinstall scripts happened to be in there. On your laptop.
Now hand that engineer AI. DORA's ROI report puts it politely - AI without engineering excellence just scales your problems. Except it's not more of everything.
Two weeks later you're working through lunch, you're working through dinner, and Slack never stops. Deployment frequency is up. Incidents are up worse. So who was that program actually protecting?