We tackle the elephant in the room: will AI take our jobs? Spoiler alert - probably not, but your job will definitely change shape. Ryan and Luca dig into what software development actually is (hint: it's not just mashing keyboards), why embedded systems might be particularly safe from AI disruption, and what we can learn from the Luddites and steam engines.

Drawing on Luca's experience with DevOps transformations and Ryan's work running a company, we explore why engineers keep solving the wrong problems, what Black & Decker actually sells (it's not drill bits), and why vibe-coding your email server is a terrible idea. The real question isn't whether AI will replace you - it's whether you understand what your actual job is in the first place. Plus: Pokemon evolution as career advice, and why AI is the new Agile fairy dust.

Key Topics:

• [02:30] The real job vs. the mechanical task - why writing code isn't actually your job
• [08:45] Why embedded systems are particularly safe from AI disruption - complexity, hardware interaction, and undocumented quirks
• [15:20] The Black & Decker lesson: selling holes in walls, not drill bits - understanding what customers actually want
• [22:10] Historical parallels: steam engines, DevOps, and why demand grows faster than automation
• [28:40] The reality check: most developers aren't using AI systematically yet - you're not behind the curve
• [32:15] AI as the new Agile fairy dust - why magic solutions never work without process and understanding

Notable Quotes:

"Your job is not writing code. Your job is making product. If you think about the Luddites, their job was not operating a loom. Their job was making clothes." — Ryan Torvik

"Writing code is really the smallest part of software development. Most of it is sitting in front of the screen, looking up and to the left, and figuring out what code to write." — Luca Ingianni

"The CEO of Black & Decker was once quoted as saying: We are not in the business of selling drill bits. We are in the business of selling holes in the wall. If we had laser cannons that made holes in walls, people would buy the laser cannons instead." — Luca Ingianni

Resources Mentioned:

• Agile Embedded Podcast Slack - Community discussion channel where you can reach Ryan and Luca, with a dedicated sub-channel for Embedded AI topics
• Luca's Website - Contact Luca for consulting on using AI effectively in embedded systems contexts - multiple contact options available

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