Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

AI Security Table

AI Security Table artwork

Is Spec-Driven Development Already Dead

Jul 15, 202642 minAudio

Can a detailed specification make AI-generated software reliable, or does it simply move the ambiguity somewhere else? Chris Romeo, Izar Tarandach, and Matt Coles revisit spec-driven development and the promise that an agent can turn written intent into a correct implementation. They debate why earlier approaches struggled, whether natural language is enough, and how tests can fail when the same AI writes both the code and its checks. The conversation explores bounded models, the Phoenix idea of regenerating disposable code, and the choice between patching a defect and rebuilding from the specification. The security question remains: if an architectural flaw survives in the spec, what stops every new implementation from reproducing it? Mentioned in this Episode: ➜ React Chapters: 00:00:00 - Intro: travel and movie reviews 00:07:23 - What is spec-driven development? 00:12:46 - Repeatability and implementation variation 00:14:50 - How do you verify generated code? 00:16:10 - Test-driven development and weak AI tests 00:20:07 - Engineering discipline and historical specs 00:24:36 - Bounding a model for a specific ecosystem 00:27:37 - Is spec-driven development already dead? 00:28:27 - Ephemeral code and the Phoenix idea 00:29:12 - Patch the bug or regenerate the application? 00:32:43 - Who is the better developer? 00:33:54 - What you want versus what you asked for 00:40:05 - Final thoughts Follow AI Security Table: ➜ Home: https://securitytable.ai/ ➜ X: https://x.com/SecTablePodcast ➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/ ➜ YouTube: https://www.youtube.com/@AISecurityTable

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Claude Code Said ‘Don’t Ask Again.’ Then It Leaked Your Secrets to GitHub

    Nov 18, 202642 minAudio

    Click “Yes, and don’t ask again” in Claude Code and it saves the exact command you approved, password and all, into a local settings file that keeps turning up in public GitHub repos. We start by admitting we all run...

    Credit the people on this episode

  2. Stop Patching Bugs, Just Rewrite It… Says the Guy Selling the Tokens

    Nov 11, 202650 minAudio

    Cisco's president handed a 27 year old engineer unlimited AI tokens and 24 months to rewrite 98 percent of the company's legacy code, and Sam Altman now says we can no longer just patch all the bugs. Chris sees a step...

    Credit the people on this episode

  3. You Don't Trust AI. So Why Are You Shipping Its Code?

    Nov 4, 202650 minAudio

    Sam Altman told a Stanford audience he no longer thinks we can just patch all the bugs, and the AI Security Table can't agree on whether that is news. Chris argues a swarm of subagents can tear through a repo and drive...

    Credit the people on this episode

  4. Anthropic Ditched Git. Here’s Why Your Agents Will Too

    Oct 28, 202645 minAudio

    Anthropic got tired of Git. With merges jumping from about 2,500 a day in May to more than 30,000 by September, a seven person team built Scion, a centralized, always online source control system designed for agents...

    Credit the people on this episode

  5. Don't Yell at Claude

    Oct 21, 202644 minAudio

    The White House has ordered federal agencies to stop saying AI and start saying Super Intelligence, and the hosts want to know whether anything actually changed overnight. Matt walks through the executive order and the...

    Credit the people on this episode