Episode Player

In this episode, we take on spec-driven development, the resurgent idea that writing a detailed spec and letting AI implement it will finally give us the precision engineering promised us since the 1950s. We push back on the notion that this fixes what actually sank spec-driven approaches decades ago: specs were never the problem; following them was. Along the way, we debate whether AI-generated code is any more correct than what a room of human developers would produce, dig into the "Phoenix" analogy of regenerating disposable code from spec instead of patching it, and raise the uncomfortable question of what happens when an integration quietly regenerates itself around a security flaw baked into the system it connects to. 

🚀 Join the Conversation
 If the AI can regenerate your code from spec whenever a bug shows up, who's actually responsible when it regenerates the same vulnerability?

FOLLOW OUR SOCIAL MEDIA:

➜Twitter: @SecTablePodcast
➜LinkedIn: The Security Table Podcast
➜YouTube: The Security Table YouTube Channel

Thanks for Listening!