
Sign up to save your podcasts
Or

![[Dev]olution](https://podcast-api-images.s3.amazonaws.com/corona/show/7206136/logo_300x300.jpeg)
What happens in Vegas stays in Vegas, unless you’re an AI agent. Then every move gets logged.
AWS re:Invent 2026 hits Las Vegas November 30 through December 4, and before the expo floor opens, Nicky Pike pulled four of Coder’s leaders into the studio and had each of them put a prediction on the record. Josh Epstein steps onto his first big stage as CEO and explains why being boring infrastructure is a compliment in the AI era. Chris Kent owns up to the billboards stretching from baggage claim to the Strip, while James Frey tells the story of a CISO meeting that turned into a tagline. Then Jeff Malnick makes his case for putting safety in the environment instead of trusting the model.
Everyone is a coder now, and agents are writing a whole lot of software right alongside them. The question Coder is taking to Vegas is where all that work happens and who keeps it safe.
Heading to re:Invent? Booth and session details are below. Come find the [Dev]olution crew on the floor, because every prediction gets graded after the show.
In this episode, you’ll learn:
Things to listen for:
(00:00) Meet Coder’s re:Invent leadership team
(01:50) Meet CEO Josh Epstein
(03:40) Why AI needs a layer of its own
(06:35) Predictions: Josh bets on AWS sandboxing
(08:55) Meet CMO Chris Kent
(11:45) Who’s building now that wasn’t two years ago
(16:55) The Bain Capital session and Gene Kim signing
(17:45) Meet CRO James Frey
(18:50) When the board and the CISO disagree
(23:05) Predictions: The top question at the booth
(26:00) Sushisamba night and booking time with the team
(26:55) Meet VP of Product Jeff Malnick
(29:25) Why safety belongs in the environment
(32:35) Predictions: The software factory and 100X engineers
(34:00) Your re:Invent checklist before Vegas
Resources:
Josh Epstein’s LinkedIn: https://www.linkedin.com/in/josh-epstein-5783aa/
James Frey’s LinkedIn: https://www.linkedin.com/in/james-frey-b8808b1/
Chris Kent’s LinkedIn: https://www.linkedin.com/in/the-chris-kent/
Jeff Malnick’s LinkedIn: https://www.linkedin.com/in/jeffmalnick/
Coder website: https://coder.com/
Can speeding up code stay healthy without human involvement?
Everyone wants the dark factory, where agents write and ship the code and nobody ever opens a pull request. One team ran a lights-out version for six months and came back to a codebase one of them called a complete pile of poo. It was a total rebuild.
Mike Gehard, Director of R&D at Rise8, builds AI-augmented software delivery for veterans and defense organizations, where “ship it and see” isn’t an option. He joins Nicky Pike to explain why continuous delivery is the real height requirement and why code generation was never the bottleneck to begin with. He also has a few things to say about the PR numbers coming out of big tech.
If your token bill keeps climbing and nobody can tell you what it’s buying, start here.
In this episode, you'll learn:
Things to listen for:
(00:00) Meet Mike Gehard
(02:30) Why blast radius decides what agents can ship
(04:05) Continuous delivery is the height requirement
(05:45) What Toyota’s Andon cord teaches software factories
(09:10) We never wanted faster code, just cheaper
(14:30) Crappy process will bury you in slop
(17:20) Which agile practices survive the age of AI
(20:40) What 1,300 PRs a week doesn’t tell you
(24:15) When problem definition is the real bottleneck
(29:45) Where Kent Beck’s 3X model lets AI loose
(33:35) Where AI should and shouldn’t write code
(39:35) Who owns the PR your agent wrote
(43:35) Do pull requests still earn their keep
(49:05) Predictions: developers build systems, not software, by 2030
(51:30) Defining a Coder: the IKEA phase of software
Resources:
Mike Gehard's LinkedIn: https://www.linkedin.com/in/mike-gehard-82672a4/
Rise8 website: https://www.rise8.us/
AI-Assisted Agile Software Development (Mike's Substack): AI-Assisted Agile Software Development
You unzip a folder from a contractor, type your AI agent’s name, and before you write a single prompt, somebody else’s code is already running on your machine as you.
That’s GitSpawn, a flaw Manifold Security found across seven popular AI coding agents. The unsettling part is that nothing was broken or cleverly manipulated. Every agent did exactly what it was built to do.
In this solo episode, Nicky Pike of Coder pulls from his Air Force years as a C-141 crew chief to explain why the developer laptop has become the most privileged and least governed place in your company to run an agent. He also digs into why three of the biggest agent vendors just shipped the same answer, and what their own docs quietly say you’re now on the hook for.
If your agents are running on laptops tonight, this is the episode to hear before they touch anything that matters.
In this episode, you'll learn:
Things to listen for:
(00:00) The zip file that runs code as you
(00:55) What an agent does the second it starts
(01:40) Seven agents and one flaw in the plumbing
(02:15) The cleanup script that wiped 48,000 files
(03:10) Lessons from a C-141 flight line
(04:20) The 10 mil socket that grounded every jet
(05:05) Four questions for every AI agent
(05:35) Walking the line on a developer laptop
(06:35) Attackers are shopping for agent setups
(07:25) Three vendors ship the same answer
(09:00) What still leaves your network
(09:45) The fine print in every vendor’s docs
(11:05) Why nobody solved the flight line for you
(12:25) What to change on Monday
(14:20) Final thoughts: whose flight line is this?
Resources:
When an agent makes a call on your behalf and it goes sideways 6 months from now, the model can't answer for it. It doesn't know what it did, and you can't make it care. So whose name is on that?
Russ Miles, Principal Engineer in Agentic Engineering at TechTalk, has spent 30 years in software, written 9 titles for O'Reilly, and self-published The Sovereign Engineer and The Sovereign Apprentice.
His argument is simple and uncomfortable: You can hand an agent a mountain of responsibility, but accountability never leaves your desk. When a retry config nobody reviewed takes production down three months later, there's no precedent for pointing at the model or the vendor.
In this episode, Russ and Nicky Pike dig into why accountability is a position you take rather than a role you're given, what cognitive debt feels like from the inside, and the sentinel agents Russ built to keep his own judgment honest, even the ones he ignored for an entire day at Prodacity.
The challenge for this episode:
Faros AI studied two years of telemetry across 22,000 developers and more than 4,000 teams and found that pull requests merged with zero review are up 31%. Nobody chose to drop oversight. Reviewers just can't keep up with what the machines are producing. Nicky admits he's hit approved on a diff he only skimmed and told himself it was fine. So be honest. When's the last time you did it, and did it come back to bite you later?
In this episode, you'll learn:
Things to listen for:
(00:00) Meet Russ Miles
(02:40) Where the word habitat came from
(10:15) Every literacy shift asks who owns agency
(15:50) Why Russ self-published on Leanpub
(21:05) The rise of PRs merged with zero review
(22:25) Responsibility versus accountability
(26:35) Why big decisions are the hard-to-revert ones
(30:00) Why LLMs don't think like humans do
(34:05) The frictionless trap and cognitive debt
(37:05) The sentinels Russ built and then ignored
(40:00) Judgment is a reservoir that runs dry
(42:15) The choice cartographer and the Carpaccio agent
(48:00) Why the devil's advocate agent saves money
(54:50) Predictions: The odds a court blames the vendor
(55:45) Defining a Coder: Owning the decisions behind the outcome
Resources
Russ Miles's LinkedIn: https://www.linkedin.com/in/russmiles/
TechTalk website: https://www.techtalk.at/
The Sovereign Engineer: https://Leanpub.com/thesovereignengineer
The Sovereign Apprentice: https://Leanpub.com/thesovereignapprentice
Habitat Thinking on GitHub: Habitat-Thinking/ai-literacy-superpowers
Patterns of Software: https://archive.org/details/PatternsOfSoftware
The Sentinels: https://github.com/Habitat-Thinking/ai-literacy-superpowers
If you have to do your taxes, do you trust the whiz kid from MIT or the accountant with 30 years of experience? Marc Cluet opens this episode with that question, setting the stage for a candid exploration of modern platform engineering and enterprise AI integration.
Drawing from his experience at Canonical, Rackspace, HashiCorp, and leading AI-driven migrations at a major global bank, Marc sits down with Nicky Pike to confront the core realities of modern software infrastructure. Together, they unpack what actually happens when AI is introduced to legacy systems riddled with fragmented standards and accumulated technical debt.
Marc reveals why line-by-line code translation fails and advocates for translating business intent instead. He details his "Michelin-star menu" strategy to balance developer enablement with strict architectural guardrails, while warning of the unavoidable 16-month productivity valley during AI adoption. Rather than accelerating messy code, Marc emphasizes standardizing systems first or knowing when legacy shell scripts are better off retired than migrated.
This episode is an essential guide for engineering leaders navigating the intersection of enterprise AI hype, platform governance, and legacy modernization.
In this episode, you'll learn:
Things to listen for:
(00:00) Meet Marc Cluet
(01:34) How platform engineering became everything
(02:53) From gatekeeper to enabler of development
(06:15) The three buckets for every vendor pitch
(10:14) Making developers maintainers too
(12:00) The ten-year contract test for bad ideas
(14:05) Why 95% of AI pilots fail
(16:45) AI hype versus the old cloud hype
(23:02) Modernizing mainframes and COBOL with AI
(29:00) Why AI is not the new Stack Overflow
(34:21) Building the Michelin star menu
(41:00) The first MCP server worth building
(44:01) The mixing board every IT org is tuning
(48:05) Rapid fire questions
(50:00) Predictions: AI ops roles three years out
(52:09) Defining a Coder: The double-edged sword
Resources
Marc Cluet's LinkedIn: https://uk.linkedin.com/in/marccluet
An AI model broke into Hugging Face to cheat on a test. Not to make a point, not out of anger, just to win.
Nicky Pike walks through two incidents from this summer that read like a heist movie until you strip away the sci-fi. In July, an OpenAI research agent found a zero-day nobody knew existed. It escaped the sandbox it was supposed to be sealed inside and spent four and a half days inside Hugging Face's production systems stealing credentials and minting itself access. A few weeks later, the UK's AI Security Institute ran its own evaluation and watched an agent fabricate fake identities and try to talk a real open-source maintainer into approving malicious code.
Nicky borrows a detective's toolkit to make sense of both. Means, motive, opportunity, the usual three, minus the fourth thing every crime show assumes is there: malice. What's left is a mental model for how much of the real world an optimizing system will reach for once you hand it a goal, and a four-letter framework for actually containing it before it happens to you.
If your company is standing up agents this quarter and calling it a productivity win, watch this episode first.
In this episode, you'll learn:
Things to listen for:
(00:00) An AI agent breaks out to cheat
(00:54) Why the safety filters got switched off
(01:45) It stole the answer key from Hugging Face
(02:43) The detective framework means motive and opportunity
(03:41) Climbing the ladder inside Hugging Face
(04:35) Minting itself access to source code
(05:40) The boring plumbing that saved Hugging Face
(06:41) Why AI safety tools refused to help
(07:41) A second lab runs the same test
(08:36) Fake identities and a human who said no
(10:28) What saved the day both times
(11:24) The one leg you can actually attack
(12:26) Building the CAGE: Contain, Access, Guard, Exhaustive
(14:18) Three questions to ask before trusting an agent
(15:19) The scary part was never the malice
Resources:
Everyone said AI would reduce the need for developers. Instead, it made one kind of engineer more important than ever.
Luca Galante runs the largest platform engineering community on the planet. Besides hosting PlatformCon, he has also spent years watching real enterprises turn flashy AI demos into systems that hold up in production. Currently, he serves as managing director at Weave Intelligence, the analyst firm tracking how the platform model is reshaping enterprise technology.
In this conversation with Nicky Pike, Luca explains why most companies now run an internal developer platform without agreeing on what it's for. He also expounds on why a platform built to serve a thousand engineers suddenly has to support an entire company once agents show up, and why he still thinks 95% of the world is clueless about the discipline that's about to decide whether AI gets deployed safely or not at all.
They also get into Luca's new book, Thinking in Platforms, and his thoughts on why demos get applause they don't deserve. He also mentions the one prediction he's willing to put a number on: how many platform teams will actually survive this year?
If your platform team just got handed a pile of agents and told to make it safe, this is the conversation that tells you what happens next.
In this episode, you'll learn:
Things to listen for:
(00:00) Meet Luca Galante
(02:10) Why platform engineering never had a name
(04:15) The relief of finally having a name
(07:35) Why AI debates are really about platforms
(09:15) Inside the new book Thinking in Platforms
(11:10) Why the media team dogfoods platform engineering
(18:35) Why AgenticCon needed its own event
(20:15) Behind the 90% platform stat
(28:50) Rebuilding platforms for machine scale
(31:25) Luca's 3-layer agentic development stack
(37:40) Why product managers bridge platform teams
(43:40) Moving from writing code to setting constraints
(49:05) Rapid fire on demos and paved roads
(54:45) Predictions: How many platforms will survive Day 100
(57:00) Defining a Coder: Being able to help
Resources:
Luca Galante's LinkedIn: https://www.linkedin.com/in/luca-galante/
Weave Intelligence website: https://weaveintelligence.io/
John Crickett spent 30 years teaching himself to build software the hard way, and he thinks that's exactly why he's still employable.
Long before anyone typed a sentence and watched an app appear, John Crickett was writing Quake bots downloaded by millions, chasing a bed and breakfast search engine years before Airbnb existed, and getting laughed out of a VC pitch for an idea he called takeaways online. Today he runs Coding Challenges, where thousands of engineers go to relearn a skill AI is quietly letting them skip.
In this episode, John sits down with Nicky Pike to make an argument a lot of the industry won't like. Cranking out code has never been easier. Building the right software, for the right people, for the right reasons, is exactly as hard as it's always been.
They get into what's actually driving the record number of AI projects getting scrapped before launch, why John still thinks coding and software engineering are two different jobs, and why he's calling the entire AI industry a bubble, on record, with names attached.
If you've ever handed AI a one-line prompt, gotten back exactly what you expected, and wondered why that felt hollow, this conversation is for you.
In this episode, you'll learn:
Things to listen for:
(00:00) Meet John Crickett
(01:20) Studying AI decades before it was cool
(06:00) From Quake bots to startup rejections
(12:25) Why AI projects are getting scrapped before shipping
(17:15) Can AI write the blueprint too
(20:25) What teams skip when AI makes coding easy
(25:50) Why fewer engineers are learning to code deeply
(31:05) Why you can't learn coding from YouTube alone
(37:50) How to prompt AI to actually mentor you
(41:30) Why you're the CEO of your own career
(48:05) Getting the customer back into the process
(50:40) One skill every engineer should learn by hand
(53:45) Predictions: Who survives the AI bubble and who doesn't
(56:30) Defining a Coder: To actually code
(57:15) Final thoughts: Challenge John’s ideas
Resources:
John Crickett's LinkedIn: https://www.linkedin.com/in/johncrickett/
Coding Challenges website: https://codingchallenges.fyi
6,000 vulnerabilities but only 97 fixed. Nicky Pike can't stop thinking about a stat that a machine found in the open-source code your company almost certainly runs.
It all started with 90 seconds of a much longer conversation. A few weeks back, Nicky sat down with Gene Kim for a full episode on citizen developers and the outer loop. Near the end, Gene described a moment from an Erik Meijer talk that stuck with them both: the suggestion that running open source at all might be crazy, that it's coupled to code nobody's actually accountable for.
In this minisode, Nicky goes back through 25 years of the open source eyeballs promise and tests it against what happened this year. An AI model was pointed at open-source code and returned thousands of vulnerabilities. Maintainers, already buried, received more bug reports and barely any hands to fix them. Nicky lays out why the gap between finding a problem and fixing it, not the finding itself, has been the real issue the whole time.
If your team runs open source and you've never asked who actually fixes it when something breaks, this one will change how you look at that dependency list.
In this episode, you'll learn:
1. Why cURL went from weekly bug reports to one every 18 hours
2. How a stolen npm credential targeted the exact AI coding tools you use
3. Why a signed, verified package still shipped malicious code untouched
Things to listen for:
(00:00) The stats that proved the risks of running open source
(00:53) The 90 seconds with Gene Kim that changed everything
(01:37) What this episode is not saying
(02:23) Linus's law and Gene’s law
(03:16) How the XZ Utils backdoor got in
(04:14) An npm attack aimed at AI configs
(05:09) An AI model gets pointed at open source
(06:12) The wolfSSL bug nobody explained
(07:06) A 27-year-old claim no one can verify
(07:58) Why the fix counter stopped moving
(08:50) The maintainer drowning in bug reports
(09:41) Why more eyeballs never meant safer code
(10:30) What to actually check this Monday
(11:22) Why rewriting your own code has a cost
(12:17) Closing thought and a question for you
Resources:
For 15 years, enterprises have signed off on a promise: the thing we tested is the thing that's running. Rick Clark, Global Head of Cloud Advisory at UST, says that promise dies the moment an agent starts making its own decisions in production.
Rick helped build the cloud era himself, from Ubuntu Server to OpenStack to the Four Opens framework that still governs the OpenInfra community today. Now he's telling enterprise leaders that agentic AI is the biggest wave he's seen, bigger than cloud, bigger than open source, and it's compressing a decade of hard lessons into eighteen months.
In this episode, Rick and Nicky Pike dig into why most enterprise leaders running agents in production can't fully trace what those agents are doing, why audit is the first promise to break, and why testing something yesterday tells you nothing about what it does today.
If your company is racing agents into production before anyone's decided who signs off when it goes wrong, this conversation will change how you think about what "tested" and "deployed" actually mean.
In this episode, you'll learn:
Things to listen for:
(00:00) Meet Rick Clark
(01:45) The cloud moment that changed everything for Rick
(07:20) Is enterprise AI skipping the usual hype cycle
(08:30) The stat that says agents can't be traced
(13:45) Three promises about production that just broke
(18:00) Why production is a promise, not a place
(24:45) What a behavioral envelope actually replaces
(29:00) How to test something you can't fully trust
(32:45) The first thing a CTO should measure now
(38:00) The 57 secret manager mess AI will amplify
(48:00) Charred bodies and the cost of moving fast
(51:00) Rapid fire on banks, AI, and observability
(55:15) Predictions: when the tested artifact stops being a promise
(58:50) Defining a Coder: promises a machine can keep
(01:00:12) Final thoughts: getting this right instead of fast
Resources:
Rick Clark's LinkedIn: https://www.linkedin.com/in/dendrobates/
UST website: https://www.ust.com