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

Ryan and Luca sit down with Shawn Hymel, an educator and course creator focused on edge AI and embedded systems. We explore what's changed in the past few years—from basic keyword spotting to full object detection on microcontrollers, thanks to integrated NPUs. Shawn walks us through the messy reality of deploying ML models to embedded hardware: vendor-specific toolchains, dependency hell, and the ongoing challenge of making edge AI accessible. We discuss what students and experienced engineers need to learn (or unlearn) to work effectively in this space, and look ahead to exciting developments like reinforcement learning on tiny devices and neuromorphic computing. It's a candid, technical conversation about where edge AI stands today and where it's headed.

Key Topics:

• [03:30] Why run ML on microcontrollers? Power, size, and application-specific advantages
• [06:00] Keyword spotting as the original killer app for edge AI
• [08:45] The game-changer: NPUs enabling full object detection on microcontrollers
• [13:20] Privacy benefits of on-device processing vs. cloud-based inference
• [16:00] How NPUs work under the hood and the vendor-specific deployment reality
• [24:30] The painful parts: dependency hell, graph compilers, and memory arena sizing
• [29:00] Using AI tools (LLMs) to navigate vendor documentation and generate code
• [33:45] What CS students and ECE students each need to learn for edge AI
• [40:15] Shifts in university enrollment: ECE rising, CS declining
• [44:00] When you don't need AI: PID loops and deterministic solutions still matter
• [47:30] Looking ahead: reinforcement learning on microcontrollers and neuromorphic computing

Notable Quotes:

"Five, six years ago, we didn't have full object detection on microcontrollers. Now with NPUs, we can do things like full YOLO on a 320x320 image—milliwatts of power, full object detection. That was not a thing five years ago." — Shawn Hymel

"Expect to spend a day or two getting inference to actually run. The docs are still new, the graph compilers are fairly new. You're going to end up in dependency hell—both on the Python side and when you bring it over to the embedded side." — Shawn Hymel

"If a PID loop solves your need, there is absolutely no reason to put AI on there. That is a solved problem. Don't do it—just use a PID loop." — Shawn Hymel

Resources Mentioned:

• Shawn Hymel's Website - Shawn's main site with links to free and paid courses on edge AI and embedded systems
• OpenMV - Computer vision platform for microcontrollers, including the new AE3 board with NPU support
• Edge Impulse - Platform that simplifies ML model deployment to embedded devices, supporting various NPUs
• Andrew Ng's Coursera ML Course - Foundational machine learning course recommended for understanding the math behind ML
• TensorFlow Lite for Microcontrollers (LiteRT) - Framework for running ML models on microcontrollers across different platforms

Ryan and Luca tackle a challenge many AI users are facing: what happens when your AI provider starts acting up? Drawing from recent experiences with Anthropic's capacity issues, secret billing practices, and model degradation, we explore practical strategies for avoiding vendor lock-in.

We discuss the three layers of complexity: the model itself, the harness (like Claude Code or GitHub Copilot), and your authored content (skills, MCP servers, prompts). Each layer presents different challenges when switching providers. Ryan shares his approach of stepping back to simpler, more granular prompting to stay provider-agnostic, while Luca experiments with maintaining escape hatches to other platforms. We also look at the realities of running local models and the tradeoffs between convenience and control. The bottom line? Pick one system, get proficient, but prepare your exit strategy - because in this volatile landscape, you'll likely need it sooner than you think.

Key Topics:

• [02:30] Anthropic's recent troubles: capacity issues, model degradation, and gaslighting users
• [06:45] The Hermes.md billing scandal - secret charges for having a specific filename
• [10:20] Ryan's approach: stepping back to simpler, granular prompting for provider independence
• [15:00] The three layers of complexity: model, harness, and authored content
• [18:30] Why models aren't interchangeable - different flavors, tokenizers, and caching strategies
• [24:15] Luca's tone-of-voice challenge: getting consistent writing style across models
• [30:00] Running local models and private inference as alternatives to frontier models
• [35:45] Practical strategies: maintaining escape hatches without parallel systems
• [40:20] Luca's solution: versioning authored content separately with symlinks

Notable Quotes:

"The more you actually make use of AI in your work, the more you use it as a force multiplier, the more painful it becomes if that force multiplier goes away." — Luca

"It's about total clock time. If you get a one shot and then have to redo it again, how much of that clock time is being used effectively?" — Ryan

"Pick one, stick with it, be proficient in it. But prepare yourself to have to escape eventually, because the situation is so volatile." — Luca

Resources Mentioned:

• Claude Code - Anthropic's AI coding assistant with hooks and skills support
• OpenCode - Provider-agnostic AI coding harness that supports multiple models
• GitHub Copilot CLI - Multi-provider AI assistant with dropdown model selection
• MCP (Model Context Protocol) - Protocol for extending AI capabilities across different harnesses
• Ollama - Tool for running local AI models on your own hardware