Get The Stack Overflow Podcast at your favorite listening service.
Ryan is joined by David Hsu, CEO and founder of Retool, to explore how AI is transforming the role of a software developer into a software architect, the increasing accessibility of coding for non-engineers, and the importance of placing guardrails and higher-level programming primitives on AI coding assistants.

Ryan talks with Deepak Singh, VP of Developer Agents and Experiences at AWS and lead at Kiro, about spec-driven development in a vibe coding world. They explore how AI tools have evolved from autocomplete to sophisticated agents that can write code based off of just specs, and how AWS has pioneered spec-driven development through their Kiro agent.

Stack Overflow, born on the bare metal racks of a data center, ascends to the cloud.

Kathleen Vignos, VP of Software Engineering at Capital One, sits down with Ryan to explore shifting to 100% serverless architecture in enterprise, deploying talent for better customer experience, and fostering AI innovation and tech advancements in a regulated banking environment.

Ryan welcomes Jeu George, cofounder and CEO of Orkes, to the show for a conversation about microservices orchestration. They talk through the evolution of microservices, the role of orchestration tools, and the importance of reliability in distributed systems. Their discussion also touches on the transition from open-source solutions to managed services, integration opportunities for AI agents, and the future of microservices in cloud computing.

At HumanX 2025, Ryan chatted with Rodrigo Liang, cofounder and CEO of SambaNova, about reimagining 30-year-old hardware architecture for the AI era.

Ken Stott, Field CTO of API platform Hasura, tells Ryan about the data doom loop: the concept that organizations are spending lots of money on data systems without seeing improvements in data quality or efficiency.

On this episode Ryan and Stack Overflow Director of Brand Design David Longworth chat with Matt Biilmann, CEO and co-founder of Netlify, about composable architecture, how making it easier to code will create more developers, and why the future of the front end is portability.

MVC is an old pattern, but it's still relevant to web apps.

While the future may be a mystery, you can design software to accommodate future changes. But how much future-proofing gets in the way of good design?

Do you design software with a big requirements doc upfront or let architecture emerge during agile processes? Is there a middle ground?

While computing has changed a lot in the 20 years since the SOLID principles were conceived, they are still the best practices for designing software.

This is a story about trying to rethink complex systems: the challenges you face when you try to rebuild them, the burdens you face as they grow, and how inaction itself can cause it’s own problems. When you’re weighing the risk and reward of replacing architecture, it can take several attempts to find a solution that works for you.

One of the tough decisions you and your team may face as you scale is deciding between keeping your current codebase and rebuilding on a new architecture.
