DOP 315: Why Good Developers Spend More Time Designing Than Coding
Release Date: 09/10/2025
DOP 342: Your Company Documentation Is Useless for AI
DevOps Paradox
#342: Most companies have plenty of documentation. The problem is almost none of it is findable, current, or true. Between what's documented, what's actually true, and what people actually do, there are gaps wide enough to kill any AI initiative before it starts. Viktor makes a distinction that reframes the whole problem: there are two types of documentation. Why something was done -- that's eternal. How something works -- that's outdated the moment someone changes a config and forgets to update the wiki. The information about that change probably exists somewhere -- in a Zoom recording, a...
info_outline
DOP 341: AI Widened the Highway but Nobody Rebuilt the Bridge
DevOps Paradox
#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...
info_outline
DOP 340: Why Operations Teams Resist Every Technology Wave
DevOps Paradox
#340: The smartest ops people are often the most likely to resist new technology -- and they're not wrong. If you don't change anything, nothing breaks, and nobody blames you. That's a completely rational choice. It's also the one that guarantees you fall behind. Bare metal to VMs, VMs to cloud, cloud to Kubernetes -- every time, the teams that played it safe ended up scrambling to catch up two years later. The safe bet isn't safe. It just feels that way. It gets worse when you look at where the tools come from. Kubernetes? Built by developers. Terraform? Developers. Containers? Developers....
info_outline
DOP 339: DNS Is Old Tech (And That's Why It Still Runs the Internet)
DevOps Paradox
#339: DNS has been around since the 1980s. Nobody's writing blog posts about how it changed their life. But every single thing on the internet depends on it -- including all those AI tools everyone's excited about. Anthony Eden has been in the DNS business since the late nineties, when he was CTO of one of the first seven domain registrars after the .com deregulation. In 2010 he started DNSimple, and he did it without a dime of venture capital. Sixteen years later, his 20-person team runs a global DNS infrastructure with 14 edge nodes and 9 origin servers spread across multiple continents. The...
info_outline
DOP 338: The Assembly Line Problem: Why Adding AI to One Step Breaks Everything
DevOps Paradox
#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...
info_outline
DOP 337: Nanoseconds Matter - InfluxDB and the Future of Real-Time Data
DevOps Paradox
#337: Time series databases have become essential infrastructure for the physical AI revolution. As automation extends into manufacturing, autonomous vehicles, and robotics, the demand for high-resolution, low-latency data has shifted from milliseconds to nanoseconds. The difference between a general-purpose database and a specialized time series solution is the difference between a minivan and an F1 car - both will get around the track, but only one is built for the demands of real-time operational workloads. The open source business model continues to evolve in unexpected ways. While...
info_outline
DOP 336: Why Top Talent Won't Work for You Anymore
DevOps Paradox
#336: The workplace is on the verge of a transformation as significant as the Industrial Revolution. Just as Bring Your Own Device policies emerged after the iPhone disrupted corporate mobile standards, we are now entering an era where employees may arrive with their own AI teams in tow. The question is no longer whether AI will change hiring and employment - it is how quickly companies will adapt before being left behind by competitors who embrace this shift. Current AI productivity gains remain largely individual rather than organizational. Writing code twice as fast means nothing if the...
info_outline
DOP 335: Stop Building Dashboards and Start Getting Answers With Coroot
DevOps Paradox
#335: Observability tools have exploded in recent years, but most come with a familiar tradeoff: either pay steep cloud vendor markups or spend weeks building custom dashboards from scratch. Coroot takes a different path as a self-hosted, open source observability platform that prioritizes simplicity over flexibility. Using eBPF technology, Coroot automatically instruments applications without requiring code changes or complex configuration, delivering what co-founder Peter Zaitsev calls opinionated observability—a philosophy of less is more that aims to reduce cognitive overload rather than...
info_outline
DOP 334: If Code Is the Easy Part, What Should Developers Actually Be Doing?
DevOps Paradox
#334: The debate over whether AI saves developers time misses a fundamental truth: coding was never the hardest part of software development. Writing code is mechanical work - the real challenges have always been understanding problems, designing solutions, communicating with stakeholders, and navigating organizational complexity. AI is now forcing a reckoning with this reality, pushing developers at every level to reconsider what skills actually matter. The traditional separation between architects who design and developers who implement is breaking down. AI enables a return to something like...
info_outline
DOP 333: The Hidden Problems Behind Every Data Pipeline
DevOps Paradox
#333: Pete Hunt, CEO of Dagster and early React team member, explores the evolution from Facebook's early React development through trust and safety infrastructure at Twitter, to building modern data orchestration tools. The conversation reveals how similar infrastructure problems plague every industry - whether you're launching rockets or managing porta-potties, the core challenges remain consistent: late data, quality issues, and mysterious errors that require both automated solutions and human oversight. The discussion dives into the technical realities of scaling systems, from the...
info_outline#315: In this episode, the discussion centers around the critical importance of design over mere code writing in software development. The hosts reflect on their experience with coding tools like Cursor and Claude Code, noting their pros, cons, and the efficiency brought by AI in handling coding chores. They highlight the paradigm shift in developer tasks from writing code to managing and designing projects, comparing it to the role of an author in world-building. The conversation also touches on the potential future of startups leveraging AI to minimize costs, the iterative nature of design, and practical tips for integrating AI into development workflows effectively.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at: