#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/

#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/

#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/

#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/

#331: At the end of 2024, predictions were made about what 2025 would bring to the tech industry. A year later, on New Year's Eve, it's time to look back and see what actually happened. The prediction episode from January 1st covered four major topics: rug pulls from companies switching to business source licenses, the rise of WebAssembly adoption, a wave of company acquisitions, and AI becoming embedded in existing tools. Some predictions hit the mark while others missed entirely, but what emerged was something nobody fully anticipated.

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/

#330: In this short episode, Darin and Viktor reflect on the holiday season.

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/

#329: Vibe coding - the practice of casually prompting AI to generate code solutions - has become increasingly popular, but its limitations become apparent when applications need to scale beyond personal use. While AI-assisted development can be powerful for proof of concepts and small internal tools, the transition from vibe-coded solutions to production-ready applications often requires experienced engineers to rebuild from scratch.

The conversation explores three distinct levels of software development: personal tooling, internal applications, and public-facing systems. Each level demands different approaches, with vibe coding being most suitable for the first category but potentially problematic as complexity increases. The analogy of cooking illustrates this well - anyone can make a simple meal, but feeding hundreds of people requires professional expertise and proper infrastructure.

Technical debt in the AI era presents new challenges and opportunities. Traditional software engineering principles like DRY (Don't Repeat Yourself) and clean code practices may matter less when AI can quickly refactor and improve code. The future likely involves hybrid teams where business experts work alongside experienced engineers, with AI agents handling implementation details. Darin and Viktor examine how pair programming is evolving from developer-to-developer collaboration to human-to-AI partnerships, fundamentally changing how software gets built and maintained.

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/

#328: The build versus buy decision isn't as binary as most companies think. Every technology choice involves elements of both - you might use Linux (buy) but still configure and customize it extensively (build). The real question isn't whether to build or buy, but finding the right balance between the two approaches based on your company's resources, size, and unique requirements.

Companies often fall into the trap of thinking their processes are so unique that existing solutions won't work, leading to unnecessary custom development. This "not invented here" syndrome is particularly common in large enterprises that mistake their size for complexity. In reality, most businesses face challenges that have already been solved by others. The key is recognizing when you truly need a custom solution versus when you can adapt existing tools.

The decision becomes more nuanced when considering factors like maintenance costs, compliance requirements, and long-term sustainability. Building internally requires ongoing resources for updates, security patches, and knowledge retention within your team. Meanwhile, buying from vendors shifts much of this burden but introduces dependencies and integration challenges. The conversation features insights from Alex Gusev from Uploadcare, along with perspectives from hosts Darin and Viktor on navigating these complex technology decisions.

Alex's contact information:

X: https://x.com/alxgsv

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

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/

#327: When AI tools suggest putting glue on pizza, it's a harmless laugh. But when autonomous AI agents start managing your infrastructure, the stakes become much higher. The reality is that current AI technology isn't ready for unsupervised deployment in critical systems, and treating it like it is could lead to catastrophic failures.

The challenge isn't just about AI capabilities—it's about management and oversight. Most developers aren't trained as managers, yet they're being asked to supervise AI agents that need constant guidance and correction. Just like hiring a new employee, AI agents require company-specific knowledge, proper guardrails, and ongoing supervision to be effective. The same principles that apply to managing human workers—code reviews, testing, and performance evaluations—need to be adapted for AI management.

As the ecosystem around AI continues to evolve rapidly, new challenges emerge. From sleeper agents that activate on specific dates to the need for completely new approaches to technical SEO for LLMs, the landscape is changing faster than most organizations can adapt. Darin and Viktor explore these challenges and discuss practical approaches for keeping AI systems from going rogue while maintaining the productivity benefits they can provide.

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/

#326: Microservices architecture has evolved far beyond simple distributed systems, but most development teams are still rebuilding the same foundational patterns over and over again. Mark Fussell, co-founder of Dapr and Diagrid, explains how his team at Microsoft identified this repetitive reinvention problem and created a solution that abstracts away the complexity of service discovery, messaging, state management, and security while providing true cloud portability.

Dapr emerged from Microsoft's Azure incubations team with a clear mission: stop forcing developers to rebuild distributed systems patterns from scratch. The runtime provides standardized APIs for common microservices needs while allowing teams to swap underlying infrastructure components without changing application code. Whether using Kafka, RabbitMQ, Redis, or cloud-native messaging services, developers write against consistent APIs while platform teams maintain control over infrastructure choices.

The conversation covers Dapr's journey from Microsoft internal project to CNCF graduated status, the technical decisions behind its multi-language approach, and how it integrates with existing frameworks like Spring Boot and .NET. Mark also discusses Diagrid's platform play around durable workflows and the emerging role of Dapr in AI agent development. Darin and Viktor explore the practical adoption challenges, the balance between developer productivity and platform engineering concerns, and why experienced developers tend to embrace abstraction layers more readily than those building their first distributed systems.

Mark's contact information:

X: https://x.com/mfussell

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

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/