Podcast profile
By Darin Pope & Viktor Farcic
What is DevOps? We will attempt to answer this and many more questions.
Latest episode
49 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
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? Turns out that's a job now.
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. Want a hundred a day?
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. With your keys sitting on disk.
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. It's more of whatever you were already doing, and there's a statistical chance that what you're doing is bad.
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? In this episode, we speak with Dr.
The 90s were about getting a browser to render your page at all. The early 2000s were about SEO, or as Darin puts it, sell me all the ads ready. Run yours. You will be sad. Viktor thinks the framing is slightly off, though, and the correction is the good part.
Viktor puts it to Alex Casalboni from Unleash, who says he argues about this with his colleagues roughly every day, and the answer lands clean. Switching a hostname, a database, an API vendor? That is infrastructure, nothing to do with who the user is, so keep your canaries and your blue-green.
Every test passes - yours, theirs, all of it. And you can tell it was generated. Not assisted. Generated. What do you do with it? Viktor's first move is to poke the premise: how do you even know it was generated and not assisted? You can't. Nobody can. That distinction is already gone.
Your phone doesn't ring. You wake up to a clean incident report - the system caught the problem, fixed itself, and left a Slack note saying it handled things at 3:15. Would you trust it? Viktor wouldn't, not at first. Same as a new hire, a new tool, a new anything. Trust gets earned.