Hardware Podcasts

BONUS: Listener Question on Repository Organization

The Pragmatic Embedded Podcast · 24 Apr 2025 · 15m

What this episode covers

Luca Ingianni responds to a listener's question about repository granularity in safety-critical embedded development, arguing against the use of separate repositories for different work products. He advocates for a monorepo approach with trunk-based development, suggesting that splitting code into micro-repositories leads to architectural errors and hidden divergences. Instead, he recommends using feature flags, tagging, and CI pipelines to manage configuration and isolation within a single repository. The discussion highlights the trade-offs between auditability and the visibility required for effective collaboration and early bug detection.

Most relevant to

early-stage companies

Topics

Mentioned

Tools
Renovate bot
Also
John Taylor's Embedded Project Cookbook, Trunk-Based Development, Minimum CD Podcast

Related episodes from other shows

Other shows on the same ground, closest first.

  • Oxide and Friends · 1h 30m

    On Code Review

    Bryan Cantrill, Adam Leventhal, and Kendall Morgan discuss the nuances of code review, contrasting modern digital tools with historical in-person practices at Sun Microsystems. They share specific war stories, including a DTrace integration bug caused by removing a single interrupt line and an n^3 algorithm in SCSI target code, to illustrate the importance of context and scale. The group debates the value of empathy, tooling choices like GitHub and Gerrit, and strategies for introducing code review cultures in organizations that resist them.

    Embedded firmware
    8 chapters

  • Embedded.fm · 1h 24m

    250: Yolo Snarf (Repeat)

    Chris Svec, a senior principal software engineer at iRobot, joins the Embedded.fm hosts to discuss the critical importance of version control in professional software development. They use a D&D-style scenario to explain how to evangelize version control to different stakeholders, including interns, managers, and electrical engineers, highlighting benefits like history tracking, rollback capabilities, and release management. The conversation covers practical aspects of using systems like Git and SVN, including branching strategies, commit messages, and the differences between centralized and distributed version control.

    Embedded firmwarePCB design & layout
    10 chapters

  • Embedded.fm · 1h 06m

    191: What, Yogurt!?!

    Hosts Elecia White and Christopher White answer listener emails, covering topics from I2C pitfalls and RTOS choices to advice for students and engineers dealing with legacy code. They discuss the 'March Micro Madness' dev kit tournament, automation in embedded testing, and the challenges of refactoring a 60,000-line monolithic codebase. The episode also includes career advice for undergraduates and a discussion on short stories.

    Embedded firmwareCareers & education
    9 chapters

  • Embedded.fm · 1h 23m

    440: Condemned to Being Perfect

    Elecia White and Chris White host a crossover episode with Jeff Gable and Luca Ingianni of the Agile Embedded podcast to debate the application of Agile principles to embedded systems. The group discusses redefining Agile as 'risk management through feedback loops' rather than rigid Scrum, and explores the challenges of scaling these practices in large enterprises versus small teams. They also tackle specific technical debates, including the role of unit testing, the definition of Minimum Viable Products (MVPs) for hardware, and the necessity of documentation in regulated industries like medical devices.

    Embedded firmwareLeadership, teams & culture
    6 chapters

  • The Amp Hour · 1h 19m

    Firmware for Hardware Engineers with Phillip Johnston

    Phillip Johnston of Embedded Artistry explains how hardware engineers can improve firmware quality by adopting software engineering practices like separation of concerns, information hiding, and loose coupling. He details the implementation of Continuous Integration (CI) pipelines using tools like Jenkins and GitHub Actions to automate testing, static analysis, and hardware-in-the-loop checks. Johnston also discusses the strategic shift from bare-metal development to ecosystems like Zephyr RTOS and the importance of designing for change to mitigate supply chain risks.

    Embedded firmwareDebugging & failure analysis
    7 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.