Test-Driven Development in the Age of AI

The Pragmatic Embedded Podcast · 18 Mar 2026 · 42m

What this episode covers

Luca Jani, an embedded systems expert and host of the Embedded AI Podcast, explains his test-driven development (TDD) workflow using Claude Code, arguing that TDD provides essential control and confidence when AI generates code. He details a three-phase process—test ideas, test outlines, and test implementations—to prevent 'success theater' where AI creates overly generous, weak assertions. The conversation highlights that the real bottleneck in AI-assisted development is expressing clear intent and specifications, not code generation speed, and emphasizes that developers must maintain tight conceptual control while treating AI as a pair programmer.

Other shows on the same ground, closest first.

  • Embedded.fm · 1h 10m

    270: Broccoli Is Good Too

    James Grenning, author of 'Test Driven Development for Embedded C' and founder of Wingman Software, discusses the philosophy and practice of Test Driven Development (TDD) for embedded systems. He explains how TDD reduces debugging time by enforcing small, verifiable steps and using techniques like 'ZOMBIES' to defer complex decisions. Grenning also shares insights from a recent side project involving a Synapse Wireless mesh network for industrial water pressure monitoring, illustrating how to handle hardware uncertainty through experimentation and loose coupling.

  • Embedded.fm · 57m

    30: Eventually Lightning Strikes (Repeat)

    James Grenning, author of 'Test-Driven Development for Embedded C' and founder of Renaissance Software, explains how Test-Driven Development (TDD) improves embedded software engineering by enabling developers to write portable, modular code before hardware is available. He argues that TDD forces early design decisions, such as modularity and interface segregation, which reduces integration bugs and allows engineers to test logic on a PC rather than waiting for target hardware. Grenning also discusses his teaching methodology, emphasizing that engineers should experience TDD themselves to understand its value in reducing late-stage debugging and managing legacy code.

  • OnTrack · 56m

    Embedded Systems Engineer Discusses AI-Driven Testing Revolution

    Ari Mahpour, an Embedded Systems Engineer at Rivian with prior experience at NASA JPL and Virgin Hyperloop, discusses the integration of AI and DevOps into embedded hardware development. He demonstrates 'vibe coding' with an Arduino using voice commands and LLMs, explaining how AI agents can autonomously write, compile, and test firmware. Mahpour also covers the challenges of managing hardware revisions, the importance of Model Context Protocol (MCP) for tool guardrails, and the future of AI in automated PCB design and testing.

  • Embedded.fm · 53m

    16: Democracy Is the Worst Form of Government

    Curtis Cole, a veteran embedded systems engineer and former VP of Engineering at Leapfrog, argues that Agile methodologies like Scrum and Test-Driven Development (TDD) are effective for embedded software when adapted to hardware constraints. He explains how user stories, sprints, and story points allow teams to manage unknown requirements and deliver incremental, usable prototypes without compromising the final product's stability. Cole emphasizes that Agile is merely a process tool; success depends on hiring skilled engineers who prioritize quality, testing, and modular design over mere speed.

  • Embedded.fm · 57m

    109: Resurrection of Extreme Programming (Repeat)

    James Grenning, founder of Wingman Software and author of 'TDD for Embedded C', discusses the resurgence of Extreme Programming and Test-Driven Development (TDD) for embedded engineers. He explains how TDD prevents bugs and improves code quality, contrasting it with the micromanagement often associated with modern Scrum. Grenning also details his methods for teaching TDD, including the use of CyberDojo for remote training and 'Training from the Back of the Room' techniques to engage students.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by The Pragmatic Embedded Podcast. The episode itself belongs to its publisher.