Hardware Podcasts

Crossover with Mob Mentality part 1

The Pragmatic Embedded Podcast · 16 Oct 2025 · 48m

What this episode covers

Jeff Gable and Luca Johnny of the Agile Embedded Podcast join Chris Lucian and Austin Chadwick of the Mob Mentality Show to discuss bridging hardware-software gaps in embedded systems. They argue that hardware abstraction layers and decoupling strategies allow embedded code to be tested on PCs, while mob programming eliminates silos between electrical, mechanical, and software engineers. The group highlights how mobbing improves flow efficiency and reduces documentation overhead in safety-critical medical device development by integrating all necessary roles into a single team.

Most relevant to

early-stage companies and companies scaling up

Topics

Mentioned

Also
Agile Embedded Podcast, Mob Mentality Show, D-Wave, Bob Martin, Ryan Torvik

Related episodes from other shows

Other shows on the same ground, closest first.

  • 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 firmwareLeadership, teams & culture
    8 chapters

  • Embedded.fm · 1h 09m

    103: Tentacles Of the Kraken

    Mark VanderVoord, lead maintainer of the open source testing frameworks Unity and CMock, explains how test-driven development (TDD) and mocking help embedded engineers design better code without needing full hardware simulators. He details the workflow of using CMock to generate fake interfaces for hardware drivers like I2C, allowing developers to test logic in a native host environment. VanderVoord also discusses the challenges of maintaining these tools, his new online course on ThrowTheSwitch.org, and the business model of supporting free open source projects through books and classes.

    Embedded firmwareEDA & CAD tools
    7 chapters

  • 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.

    Embedded firmwareCareers & education
    9 chapters

  • 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 firmwareDebugging & failure analysis
    8 chapters

  • Embedded.fm · 56m

    347: Be Careful About the Bits

    Elecia White and Christopher White discuss API design strategies for embedded systems, emphasizing the use of abstraction layers and the POSIX model (open, close, read, write) to manage hardware interactions. They address a listener's question about organizing firmware modules, suggesting block diagrams to define hardware, control flow, and layered interfaces. The hosts also tackle a career dilemma involving a startup engineer who feels demoted after being acquired by Big Tech and assigned to work with a senior 'gray-beard' engineer, advising on how to navigate team dynamics and imposter syndrome.

    Embedded firmwareCareers & education
    5 chapters

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.