TopPodcast.com
Menu
  • Home
  • Top Charts
  • Top Networks
  • Top Apps
  • Top Independents
  • Top Podfluencers
  • Top Picks
    • Top Business Podcasts
    • Top True Crime Podcasts
    • Top Finance Podcasts
    • Top Comedy Podcasts
    • Top Music Podcasts
    • Top Womens Podcasts
    • Top Kids Podcasts
    • Top Sports Podcasts
    • Top News Podcasts
    • Top Tech Podcasts
    • Top Crypto Podcasts
    • Top Entrepreneurial Podcasts
    • Top Fantasy Sports Podcasts
    • Top Political Podcasts
    • Top Science Podcasts
    • Top Self Help Podcasts
    • Top Sports Betting Podcasts
    • Top Stocks Podcasts
  • Podcast News
  • About Us
  • Podcast Advertising
  • Contact
Not in our directory?
Add Show Here
Podcast Equipment
Center

toppodcastlogoOur TOPPODCAST Picks

  • Comedy
  • Crypto
  • Sports
  • News
  • Politics
  • True Crime
  • Business
  • Finance

Follow Us

toppodcastlogoStay Connected

    View Top 200 Chart
    Back to Rankings Page
    Technology

    DevOps Paradox

    What is DevOps? We will attempt to answer this and many more questions.

    Advertise

    Copyright: © PlanetPope, Inc. 2019-2023

    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    DOP 341: AI Widened the Highway but Nobody Rebuilt the Bridge Mar 11, 2026
    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.

    Trevor's contact information:

    LinkedIn: https://www.linkedin.com/in/trevorbstuart/

    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:

    https://www.devopsparadox.com/contact/


    DOP 340: Why Operations Teams Resist Every Technology Wave Mar 04, 2026
    Show notes

    #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. The tools ops teams depend on were made by a different tribe. So the pushback isn't really about whether the tech is ready or whether the risk is too high. It's about identity. 'Not my people' is a harder objection to overcome than 'not ready yet,' because no amount of documentation or proof-of-concepts answers it.

    And about proof -- everyone wants it before they'll move. But the proof already exists. It's the tool someone on your team has been running in shadow IT for a year without any official support. If it survived that long on its own, that's stronger evidence than any pilot program. That's your roadmap. And the way in is small chunks, not grand plans. Move one service. Learn something. Adjust. Repeat.

    AI in ops follows the exact same pattern. A tool that gets you 50% of the way there for free means you can focus your expertise on the other 50%. That's a win. But the people waiting for AI to be perfect before they'll touch it? They're making the same mistake as the teams that waited for perfect proof before migrating to the cloud. Different decade, same trap.

    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:

    https://www.devopsparadox.com/contact/


    DOP 339: DNS Is Old Tech (And That's Why It Still Runs the Internet) Feb 25, 2026
    Show notes

    #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 conversation covers the mistakes companies make with their domains -- running production DNS on a registrar that was never built for it, sharing logins with no access control, zero documentation on why records exist. Anthony breaks down how DNS actually works at scale (unicast vs anycast, the onion layers of resolvers), why your email deliverability problems are probably a DNS problem, and what the www vs no-www debate looks like in 2026.

    On AI tools, Anthony's take is practical. They're giving his engineers more time to think about problems instead of typing out solutions. But he's not buying the vibe coding hype -- when you run critical internet infrastructure, everyone on the team needs to understand the systems they're building. And for AI startups hoping to cash out? Most will fail. The twist you put on somebody else's model won't be a moat. It'll just become a feature for something bigger.

    Anthony's contact information: X: https://x.com/aeden Bluesky: https://bsky.app/profile/anthonyeden.bsky.social LinkedIn: https://www.linkedin.com/in/aeden/

    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: https://www.devopsparadox.com/contact/


    DOP 338: The Assembly Line Problem: Why Adding AI to One Step Breaks Everything Feb 18, 2026
    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?

    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:

    https://www.devopsparadox.com/contact/


    DOP 337: Nanoseconds Matter - InfluxDB and the Future of Real-Time Data Feb 11, 2026
    Show notes

    #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 companies like Elastic and Redis have seen hyperscalers fork their projects, a new partnership paradigm is emerging. Amazon Web Services now pays to license InfluxDB and offers it as a managed service, signaling a shift toward collaboration rather than competition. This approach benefits everyone: vendors maintain development velocity, cloud providers get workloads on their platforms, and customers receive better-supported products.

    Evan Kaplan, CEO of InfluxData, joins Darin and Viktor to discuss the trajectory from observability metrics to physical world instrumentation, why deterministic models matter more than probabilistic ones when your robot might run over your cat, and what it takes to build a sustainable open source company over a decade-plus journey.

    Evan's contact information:

    X: https://x.com/evankaplan

    LinkedIn: https://www.linkedin.com/in/kaplanevan/

    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:

    https://www.devopsparadox.com/contact/


    DOP 336: Why Top Talent Won't Work for You Anymore Feb 04, 2026
    Show notes

    #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 deployment pipeline stays the same speed. But within five to ten years, entire industries face disruption - from primary care physicians to transportation to knowledge work. Companies clinging to restrictive AI policies today risk driving away top talent who have already integrated these tools into their workflows. The intellectual property implications alone - who owns an AI stack trained on company processes when an employee leaves - will require entirely new frameworks for employment law.

    Darin and Viktor explore these scenarios through the lens of a hypothetical job interview where a candidate brings their own team of AI agents. The conversation surfaces uncomfortable questions about compensation models, corporate governance, and whether we are witnessing the emergence of a new kind of talent that blends human expertise with digital capabilities.

    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:

    https://www.devopsparadox.com/contact/


    DOP 335: Stop Building Dashboards and Start Getting Answers With Coroot Jan 28, 2026
    Show notes

    #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 drowning users in endless metrics and dashboards.

    The conversation explores how Coroot differentiates itself in a crowded market with over a hundred observability vendors. Rather than competing head-to-head with cloud giants like Datadog and Dynatrace, Coroot focuses on developers who need answers fast without building elaborate monitoring systems. The platform combines systematic root cause analysis with AI-powered recommendations, using deterministic methods to trace how errors propagate through microservices before handing off to LLMs for actionable fix suggestions.

    Darin and Viktor dig into Coroot's business model with Peter, examining why the company chose Apache 2.0 licensing instead of more restrictive options, and how staying bootstrapped with minimal angel funding allows them to play the long game without pressure to chase every hype cycle.

    Peter's contact information:

    X: https://x.com/PeterZaitsev

    Bluesky: https://bsky.app/profile/peterzaitsev.bsky.social

    LinkedIn: https://www.linkedin.com/in/peterzaitsev/

    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:

    https://www.devopsparadox.com/contact/


    DOP 334: If Code Is the Easy Part, What Should Developers Actually Be Doing? Jan 21, 2026
    Show notes

    #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 pair programming, where the person thinking through problems can now work alongside a fast executor without the old bottleneck of slow human typing. This shift means developers need stronger communication skills - the ability to explain technical decisions to non-technical stakeholders and translate business requirements into technical direction. For juniors, the opportunity is unprecedented: you can upskill faster than ever in the history of software, but only if you balance building things with actually understanding how they work.

    Darin and Viktor explore what this means for developers at every career stage, from juniors who should focus on fundamentals and end-to-end understanding, to seniors who are becoming more like editors and supervisors of AI-generated work. The developers who will thrive are those who combine real experience with a willingness to embrace change - and that combination has always been the winning formula.

    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:

    https://www.devopsparadox.com/contact/


    DOP 333: The Hidden Problems Behind Every Data Pipeline Jan 14, 2026
    Show notes

    #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 microservices complexity trap to the current AI adoption wave. Hunt shares candid insights about leadership challenges, including how well-intentioned technology recommendations can backfire, and why most data projects fail despite sophisticated multi-agent orchestration. The conversation touches on career advancement pressures that drive unnecessary complexity and the importance of focusing on actual user adoption rather than technical sophistication.

    This episode features Pete Hunt in conversation with hosts Darin and Viktor, covering everything from regular expression nightmares to the future of data infrastructure and the lessons learned from building products that people actually use.

    Pete's contact information:

    X: https://x.com/floydophone

    LinkedIn: https://www.linkedin.com/in/pwhunt/

    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:

    https://www.devopsparadox.com/contact/


    DOP 332: 2026 - The Year of Discovery Jan 07, 2026
    Show notes

    #332: AI adoption in enterprise software development is accelerating, but operations teams are lagging behind. While application developers embrace AI tools at a rapid pace, those on the ops side remain skeptical—citing concerns about determinism, control, and a general resistance to change. This mirrors previous technology waves like containers, cloud, and Kubernetes, where certain groups initially pushed back before eventually adapting. The prediction for 2026: AI will not see widespread adoption in operations despite its growing presence elsewhere in the software lifecycle.

    The bigger challenge facing organizations is not just adopting AI but transforming entire processes to take advantage of it. Improving just one piece of the software delivery pipeline—like development speed—only creates bottlenecks elsewhere. Companies cannot hand developers AI tools while keeping everything else the same and expect transformational results. The future points toward a world where experts bring their own AI agents to companies: personal toolsets trained on their experience and best practices that integrate with organizational systems.

    Perhaps the most provocative insight centers on the value of writing code itself. The argument: writing code is the easiest and least valuable part of software development. The real cognitive load comes from thinking through requirements, architecture, and design. Developers who simply translate instructions to code without deeper engagement may find themselves in real danger as AI continues to advance. Darin and Viktor explore these predictions and more as they look ahead to what 2026 might bring for DevOps, platform engineering, and the evolving role of developers.

    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:

    https://www.devopsparadox.com/contact/


    Previous 1 2 3 4 5 6 38 Next

    Related Podcasts

    Reply All

    1

    Reply All Games & Hobbies
    Inside VR & AR

    2

    Inside VR & AR Gadgets
    Note to Self

    3

    Note to Self News
    BrainStuff

    4

    BrainStuff Natural Sciences
    This Week in Tech (Audio)

    5

    This Week in Tech (Audio) News
    Hands-On Tech (Audio)

    6

    Hands-On Tech (Audio) Technology
    footer-logo

    Contact Us

    Toll Free: 844-670-7747

    Links

    • Home
    • Top Charts
    • Networks
    • Apps
    • Independents Podcasts
    • Podcast Advertising
    • Podcast News
    • Contact Us
    • About Us
    • Analytics & Insights

    Stay Connected

      Privacy, Terms of Use & Our Code of Ethics Protecting Content Creators Copyrights