
Sign up to save your podcasts
Or

![[Dev]olution](https://podcast-api-images.s3.amazonaws.com/corona/show/7206136/logo_300x300.jpeg)
Wave one was everyone grabbing a shovel and vibe-coding as fast as possible. Wave two is the bill showing up.
Rob Whiteley has watched this movie before as he ran NGINX through the last major platform shift, and now as CEO of Coder, he's watching companies rack up token bills and security holes from software nobody thought to govern.
In this episode, Rob sits down with Nicky Pike (full disclosure, Coder sponsors this show, and Rob signs Nicky's paychecks) to talk about what actually comes after the AI gold rush. They get into why the model layer is the one thing you should never lock yourself into, how to think about tiered model strategy using a tenured employee analogy, and why governance and rules are not the same thing.
Rob also breaks down the real difference between a sandbox, a workspace, and a harness, and makes the case for why an engineer driving an agent will always beat a product manager doing the same.
If your team is already sitting on a token bill nobody budgeted for, this conversation is your map for wave two.
In this episode, you’ll learn:
Things to listen for:
(00:00) Meet Rob Whiteley
(01:20) Why this wave feels different from cloud
(06:59) Betting on infrastructure, not the tools
(11:34) The Excel analogy for your job
(15:39) One customer went from 800 apps to 10,000
(17:04) Your token bill is AWS all over again
(21:40) Rating AI models like tenured employees
(24:12) Why nobody saw the token bill coming
(31:05) Governance and rules are not the same
(36:20) Why an engineer beats a PM
(40:47) Sandbox, workspace, or harness, know the difference
(46:52) Why Coder refuses to bet on one model
(56:48) Should you go vertical or horizontal
(1:04:47) Predictions: who gets usurped and who wins
(1:07:56) Defining a Coder: what it means to build
Resources:
Rob Whiteley's LinkedIn: https://www.linkedin.com/in/rwhiteley/
Coder website: https://coder.com/
What happens when the AI coder moves faster than the review process can handle?
Nnenna Ndukwe has spent 8+ years as a software engineer and now works at the intersection of AI, developer relations, and enterprise engineering strategy. As AI developer relations lead at Qodo, she spends her time helping teams separate useful AI adoption from expensive chaos.
In this episode of [Dev]olution, Nnenna joins Nicky Pike to talk about the part of AI coding most teams skip: review, verification, governance, and the outer loop where AI-generated code either gets controlled or breaks production.
They dig into why AI does not fix broken engineering systems, how rework rate exposes the truth behind AI productivity, and why better code review needs more than another stream of AI comments. What it needs, instead, are deterministic gates, developer trust, and a clear view of where AI belongs in the software delivery process.
If your team is shipping faster but fixing more, this episode will make you rethink what “AI productivity” actually means.
In this episode, you’ll learn:
Things to listen for:
(00:00) Meet Nnenna Ndukwe
(01:52) From writing code to advising leaders
(04:09) Why AI made the work more interesting
(07:02) Paying it forward in women in tech
(09:23) AI speed is breaking production
(10:30) Where the delivery jam really happens
(12:32) Why rework rate tells the truth
(15:42) Can AI review AI code
(17:21) AI amplifies your current process
(20:34) The risk of AI review slop
(23:19) Why acceptance rate matters
(26:27) Human-agent work needs better rules
(29:23) More tokens is not discipline
(36:44) Where leaders should start
(41:25) Predictions: More managing systems
(45:49) Defining a Coder: A problem-solver
(47:08) Final thoughts: Cut the noise of AI hype
Resources:
Nnenna Ndukwe’s LinkedIn: https://www.linkedin.com/in/nnenna-ndukwe/
Qodo website: https://www.qodo.ai/
Coding used to be the bottleneck. Gene Kim says that era is ending, and most companies are not ready for what comes next.
In this episode of [Dev]olution, Gene Kim, author, DevOps researcher, and founder of IT Revolution, joins Nicky Pike to talk about what happens when software is no longer built only by developers.
Gene has spent decades studying high-performing technology organizations. He’s since helped shape the DevOps movement and co-authored the books many engineers grew up reading. Now, he’s deep in vibe coding, working with leaders, doctors, military teams, and people who have never written code before.
The big question: if everyone can suddenly build, can the rest of the company keep up? Nicky and Gene get into citizen developers, broken review gates, and why the next DevOps-sized shift may be 100x bigger.
If your company is still treating AI coding like a developer productivity tool, this conversation is the reset.
In this episode, you’ll learn:
Things to listen for:
(00:00) Meet Gene Kim
(02:30) The project that changed everything
(08:55) Pair programming with non-developers
(15:45) Why AI feels like the spreadsheet revolution
(20:07) Coding isn't the bottleneck anymore
(28:11) Nobody knows what comes next
(35:01) Why AI should review AI code
(44:51) What engineering teams should change Monday morning
(50:05) AI becomes the next DevOps specialist
(53:50) Could AI replace open source dependencies?
(01:00:40) The economics of AI coding
(01:04:20) Predictions: 50x more software from non-developers
(01:11:10) Defining a Coder: Dreams becoming reality
(01:14:20) Final thoughts: Learn from the frontier
Resources:
Gene Kim’s LinkedIn: https://www.linkedin.com/in/realgenekim/
Gene Kim’s website: http://www.realgenekim.me/
IT Revolution website: https://itrevolution.com/
96% of companies are running AI agents in production. Only 21% can actually control them.
Gari Singh has watched this movie before. Three times. XML middleware, enterprise blockchain, and now AI infrastructure at Google Cloud, and every wave has the same opening act: teams rush to deploy before the platform team is even in the room.
In this episode of [Dev]olution, Nicky Pike, and Gari break down what the outer loop actually costs you when agents go ungoverned, why "Ninja IT" is the new shadow IT, and what platform engineers need to do this Monday to stop building on a foundation that's already cracking.
If you're still treating agent governance as a roadmap item, this episode is the reason to move it to the top of the list.
In this episode, you’ll learn:
Things to listen for:
(00:00) Meet Gari Singh
(02:00) What DataPower taught him about governing traffic
(04:30) AI adoption versus the blockchain free-for-all
(06:30) The stat that should scare every platform team
(09:00) Why Kubernetes took a decade but AI took 18 months
(14:30) Prompt injection and limiting the blast radius
(18:00) Ninja IT is the new shadow IT
(20:30) Automating bad processes just makes bad things worse
(25:00) Self-managed MCP versus the enterprise version
(28:30) Why YOLO mode survives elicitation
(35:00) How platform teams hold the line without becoming the villain
(39:30) The outer loop is still the bottleneck
(44:00) Three things every platform engineer should do this week
(51:00) Rapid fire with Gari
(53:30) 2028 predictions and the governance reckoning
Resources:
Gari Singh’s LinkedIn: https://www.linkedin.com/in/garisingh/
Google’s website: https://www.google.com
Everyone's asking the wrong question about open AI models and has turned the debate into a geography problem. Is it Chinese? Is it American? Can we trust it?
But the biggest AI security incident in recent memory had nothing to do with where a model came from.
In this minisode, Nicky Pike breaks down the three layers of risk hidden behind open-weight AI models and why most security conversations focus on the easiest layer to defend. From poisoned training data and sleeper-agent research to malicious Hugging Face repositories that fooled hundreds of thousands of developers, this episode separates real threats from political headlines.
If you're evaluating DeepSeek, Qwen, Llama, or any open model, this episode will change how you think about trust, ownership, and security.
In this episode, you’ll learn:
Episode highlights:
(00:00) The repo that fooled 244,000 developers
(00:35) Why everyone wants open models
(01:20) The wrong question CIOs keep asking
(02:10) The three layers of AI risk
(04:00) Anthropic's sleeper agent experiment
(06:25) How 250 documents can poison a model
(08:00) The Hugging Face malware problem
(09:20) Why banning models misses the real threat
(10:15) Self-hosting isn't a force field
(11:20) What ownership actually gives you
(13:20) 4 practical defenses that work
(16:20) Why open models are getting too good to ignore
Resources:
What if your developer community could teach you more than any AI ever could?
In this episode of [Dev]olution, Nicky Pike sits down with Pauline Narvas, former Head of Community Platforms at Vercel and incoming leader at OpenAI Codex, to unpack why human connection is thriving in the age of AI. Pauline reveals how communities are becoming the hidden engines driving learning, collaboration, and real product impact.
From guiding developers through AI-powered tools to building trust and loyalty in forums and Discord channels, she explains why skills like curiosity, communication, and caring are more critical than ever. Pauline also shares how her team uses AI to handle the tedious tasks so humans can focus on the creative, high-value work that AI can’t replace.
Discover why being part of a community isn’t optional anymore, it’s the key to thriving in modern tech.
In this episode, you’ll learn:
Things to listen for:
(00:00) Meet Pauline Narvas
(01:06) Breaking news about her new role at OpenAI Codex
(04:00) How her journey led from coding to community
(06:40) Teaching women to code and mission-driven growth
(09:20) Overcoming early obstacles and imposter syndrome
(12:00) Developers building fast with AI and its limits
(14:50) Foundations still matter when AI automates coding
(17:30) Human interaction versus AI for learning and support
(20:00) Using community to solve problems AI can’t
(24:00) Feedback loops that improve product and user experience
(26:30) Skills that matter most in the AI era
(31:00) Why human authenticity beats AI in community roles
(34:00) AI as a support tool, not a replacement
(38:00) Handling negative community interactions with empathy
(42:00) Why heart and curiosity are non-negotiable hiring traits
(45:50) Lessons on using AI and communities to amplify impact
(49:45) Engaging with the OpenAI Codex community
(55:30) What AI can’t replace and the definition of a coder
(59:00) Closing thoughts and future outlook for human connection
Resources:
Pauline Narvas’s LinkedIn: https://www.linkedin.com/in/pnarvas/?originalSubdomain=uk
Vercel’s website: https://vercel.com/
What if your AI could patch your vulnerabilities while you sleep?
In this episode of [Dev]olution, Nicky Pike talks with DaShaun Carter, Spring Advocate at Broadcom, about the growing impact of agentic AI in software development. With more companies turning to AI to accelerate development and patch vulnerabilities, DaShaun explains how AI isn't just about coding faster, it’s about automating the tasks developers hate.
From patching CVEs overnight to ensuring systems remain secure while developers sleep, AI agents are reshaping how security is handled in development. DaShaun also talks about the shift from traditional coding workflows to AI-powered environments, where agents autonomously complete repetitive tasks, allowing developers to focus on more strategic work.
Tune in to understand why AI isn’t a “nice-to-have” anymore, it’s essential to your development process.
In this episode, you’ll learn:
Things to listen for:
(00:00) Meet DaShaun Carter
(02:13) The hidden value of patching CVEs
(05:15) Should AI be writing or patching code?
(08:34) Why security automation is essential
(12:00) The rise of AI in development security
(14:48) Continuous patching: A game changer
(18:22) Shifting from traditional dev environments
(22:00) Maintaining control with AI automation
(25:06) Avoiding over-automation in development
(28:15) How agents take over repetitive tasks
(32:10) DaShaun’s Raspberry Pi-driven AI tasks
(37:30) Will AI replace traditional coding environments?
(41:45) AI agents making dev teams effective
(46:00) AI and the future of dev security
(50:30) Predictions for AI-driven development workflows
Resources:
DaShaun Carter’s LinkedIn: https://www.linkedin.com/in/dashaun/
Broadcom’s website: https://www.broadcom.com/
You think your AI is working for you…until it’s leaking your data. Welcome to Echo Leak, the zero-click exploit that can send your company’s most sensitive info to attackers, and you won’t even realize it’s happening.
Here’s how it works: an email lands in your inbox, and without anyone clicking anything, your AI system picks it up. It accesses your sensitive data from Outlook, SharePoint, Teams, and quietly ships it out through a crafted URL, all while doing exactly what you paid it to do. This isn’t a glitch. It’s a massive vulnerability.
In this minisode, we dive into the lethal trifecta, three factors that make your AI system an easy target for this type of attack. From private data access to untrusted content, to how your AI can communicate externally, it’s all laid out for you.
Learn how to protect your systems, lock down permissions, and secure your AI agents before they become the next big breach.
In this episode, you’ll learn:
Episode highlights:
(00:00) Echo Leak: How it works without any user clicks
(03:00) The "lethal trifecta" and why it's a security risk for AI
(05:40) Real-world Echo Leak examples from Black Hat and RSA
(08:00) Vendor responses and why they’re missing the point
(09:40) Understanding AI agent governance failures
(12:00) Steps to secure your AI systems against Echo Leak
(14:20) Restricting external communication and limiting data access
(16:00) Designing AI systems with security in mind
(18:00) Preparing for AI exploits like Echo Leak
Resources:
AI agents are already embedded within your infrastructure, yet the critical issue remains: no one is truly in control. In this episode, we sit down with two experts from Red Hat, Michael Epley and Sam Richman, who are actively engaged at the intersection of AI, security, and defense. Their work isn't theoretical; it's about managing systems where the stakes couldn't be higher.
Michael Epley, as Chief Architect and Security Strategist, has dedicated years to building identity and governance frameworks in environments where errors are unacceptable. Meanwhile, Sam Richman, Principal Architect for Defense, is responsible for deploying software from development environments to operational drones.
This discussion reveals some uncomfortable realities surrounding modern security and AI: the presence of AI agents operating without proper identification, the ineffectiveness of security models designed for human users when governing machine behavior, and the challenge of managing systems that cannot be thoroughly tested, predicted, or trusted.
Despite these challenges, these systems are being rolled out. If you're involved in developing AI systems or ensuring their security, this episode poses a critical question: Do you truly understand what your AI agents are doing?
In this episode, you’ll learn:
Things to listen for:
(00:00) Meet Michael Epley and Sam Richman
(02:47) Are enterprises ready for AI agents
(05:00) Why AI adoption outpaces value
(07:00) AI finding vulnerabilities humans missed
(10:58) Why AI systems are unpredictable by design
(13:00) The identity problem for AI agents
(17:00) Digital sovereignty becomes mission-critical
(21:30) AI strategy in defense and enterprise
(26:30) Why modular AI infrastructure matters
(27:30) What Kagenti actually solves
(31:00) Fixing overprovisioned AI agents
(34:30) Observability and agent behavior tracking
(38:00) AI at the edge and deployment risks
(47:30) Running AI without losing control of data
(59:00) Predictions for AI governance and agents
Resources:
Michael Epley’s LinkedIn: https://www.linkedin.com/in/epleymichael
Sam Richman’s LinkedIn: https://www.linkedin.com/in/sam-richman
Red Hat website: https://www.redhat.com
Adron Hall thinks you already missed the boat if you are still banging away at lines of code.
He watches organizations struggle with locked-down environments while the rest of the industry moves at a pace they can't keep up with. The junior pipeline is collapsing, and we are building systems on code that nobody actually understands. Vibe coding sounds like a dream until the production system crashes at two in the morning.
Adron Hall, Principal Software Engineer at Composite Thrashing Code, joins Nicky Pike to discuss why productivity gains are getting eaten by debugging and what happens when the AI agents start treating your main repo like a sandbox project.
If you are wondering if you are building faster or just debugging more, this conversation provides the reset you need.
In this episode, you’ll learn:
Things to listen for:
(00:00) Meet Adron Hall
(03:14) Why the junior developer pipeline is imploding
(05:13) How to reign in agent scope for better results
(08:31) The slow creeping dread of vibe coding
(12:50) Moving past communication cycles with prototypes
(16:50) Why shipping to production needs a human gatekeeper
(20:20) How roles shift when agents handle the workflow
(24:05) Why slinging individual lines of code is over
(29:47) Bringing a generalist approach back to computer science
(34:57) Breaking down the six types of code changes
(41:40) Why AI optimizes for plausible output instead of correctness
(52:37) Enforcing diff limits to keep human reviewers sane
(57:29) Setting up no-fly zones for sensitive code
(01:02:41) The coming hundred x shock to the tech industry
(01:11:27) What it means to be a coder in 2026
Resources:
Adron Hall’s LinkedIn: https://www.linkedin.com/in/adron/
Composite Thrashing Code blog: https://compositecode.blog/