Luca unveils WhittleSpec, his new open-source framework for AI-assisted development that challenges the waterfall assumptions baked into most coding tools. Born from frustration with frameworks like SpecKit that treat specifications as static documents, WhittleSpec emphasizes continuous learning through retros, refinement, and test-driven development. We explore why most AI coding frameworks make typing faster but don't help with the hard part—the thinking—and discuss how proper feedback loops and vertical slicing can lead to more trustworthy software.

The conversation ranges from the philosophy of whittling away what doesn't fit (versus plowing ahead blindly) to practical implementation details: specification, planning, task breakdown, TDD cycles, and retrospectives. Luca argues that professional software engineering requires systematic processes that support learning at every step, not just tools that generate code quickly. We also touch on the missing pieces in current frameworks: support for safety-critical development, long-term roadmaps, and embedded systems considerations.

Key Topics:

• [02:30] Introducing WhittleSpec and the problem with current AI coding frameworks
• [08:45] Why AI tools make the easy part easier but leave the hard part hard
• [15:20] The waterfall trap: static specifications vs. living documents
• [22:10] Mapping the landscape of AI development frameworks (SpecKit, BMAT, Kiro, etc.)
• [28:40] How WhittleSpec works: decide, specify, plan, tasks, and TDD cycles
• [38:15] The critical role of retrospectives and the 'refine' skill for course correction
• [45:30] Vertical slicing vs. layer-by-layer implementation: tracing bullets through the stack
• [51:00] Missing pieces: safety-critical development, long-term roadmaps, and embedded considerations

Notable Quotes:

"No engineer ever said, 'I wish I could type curly brackets faster.' That was never quite the bottleneck. The hard part is sitting in front of your screen and going, 'hmm.'" — Luca Ingianni

"SpecKit is just plain old horrendous waterfall. There are no provisions at all in it for learning. The idea is you specify something well enough and then you just walk away, sip a coffee, the machine does its thing. That approach has never ever worked." — Luca Ingianni

"Your initial specification is not going to be right. As you implement the actual solution, you're going to learn things that's going to change what you need to accomplish with the spec. You might need to change completely what your expectations are." — Ryan Torvik

Resources Mentioned:

• WhittleSpec - Luca's new open-source AI-assisted development framework emphasizing feedback loops, TDD, and iterative refinement
• SpecKit - GitHub's AI coding framework discussed as an example of waterfall-style specification-driven development
• Agile Embedded Slack - Community Slack channel now open to Embedded AI podcast listeners for discussion and questions
• Luca.engineer - Luca's website with links to all his projects and ways to reach him
• TulipTreeTech - Ryan's company working on AI-generated models for pre-silicon firmware validation