The Real Python Podcast Moving Towards Spec-Driven Development
10 snips
Dec 19, 2025 Marc Brooker, VP and Distinguished Engineer at AWS, delves into the world of spec-driven development versus vibe coding. He explains how writing specifications upfront can enhance collaboration and reduce errors. The conversation touches on declarative programming, highlighting its advantages over traditional methods. Marc also introduces Kiro, Amazon's new IDE designed to translate prompts into structured requirements. Learn how clear documentation and iterative updates can empower developers and improve project alignment.
AI Snips
Chapters
Transcript
Episode notes
Open-Sourcing Radar Simulation Helped His Career
- Marc released an academic radar simulator as open source during his PhD to ease publication and collaboration.
- That early open-source work helped him later when applying to AWS.
Keep Intent Centralized
- Spec-driven development keeps intent and context centralized so AI and humans don't lose track over many prompt iterations.
- Writing a specification first lets models and developers collaborate while preserving project goals.
Write Human-Readable Specs With Examples
- Write specs in human-readable Markdown with examples and 'must/should' language for clarity.
- Include code snippets, UI sketches, or formal logic when precision is required.