Hardware Podcasts

How to Get Started

The Pragmatic Embedded Podcast · 2 Feb 2021 · 36m

What this episode covers

Jeff Gable and Luca Ingianni discuss how engineering teams can transition from traditional methods to agile development in embedded systems. They outline a three-layered approach starting with tactical technical practices like version control and continuous integration to establish reliable feedback loops. The conversation emphasizes using these quick wins to build trust and demonstrate value before expanding into project management practices like sprints and user stories, ultimately aiming to improve team culture and product quality.

Most relevant to

early-stage companies

Topics

Mentioned

Companies
Bluefruit Software, Agile Embedded Academy
Also
Ingianni.eu, JeffGable.com

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

  • Embedded.fm · 1h 19m

    211: 4 weeks, 3 days

    Dennis Jackson, Director of Firmware at Element Science, discusses how software engineers can transition into embedded systems by building personal projects using low-cost hardware like STM32 Discovery boards. He advises new hires to read James Grenning’s Test Driven Development in Embedded C and Elecia White’s Making Embedded Systems, emphasizing that understanding build systems like Make and continuous integration is as critical as writing drivers. Jackson argues that the distinction between firmware and software is fading, urging engineers to apply general software best practices like unit testing and static analysis to embedded constraints. He shares his interview philosophy, which prioritizes problem-solving and code quality over syntax, and highlights the importance of establishing a reproducible build environment to ensure reliable production releases.

    Embedded firmwareMicrocontrollers & dev platforms
    11 chapters

  • Embedded.fm · 1h 19m

    211: 4 weeks, 3 days (Repeat)

    Dennis Jackson, Director of Firmware at Element Science, discusses the career path from software to embedded systems, emphasizing that practical projects and understanding core software principles are more valuable than specific hardware knowledge for entry-level roles. He advises aspiring engineers to start with cheap development boards like STM32 Discovery boards to write simple drivers, rather than relying on high-level abstractions like Arduino. Jackson also stresses the importance of adopting professional software engineering practices, such as command-line builds with Make, continuous integration, and unit testing, to ensure code quality and reliability in production environments.

    Careers & educationEmbedded firmware
    8 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.