Hardware Podcasts

53: Being a Grownup Engineer

Embedded.fm · 28 May 2014 · 1h 03m

What this episode covers

Jack Ganssle, author of 'The Art of Designing Embedded Systems' and long-time embedded industry expert, argues that firmware engineers must adopt disciplined engineering practices rather than relying on 'heroic' hacking. He discusses the necessity of requirements gathering, design reviews, code inspections, and rigorous testing to ensure safety and reliability, citing the Toyota unintended acceleration case as a failure of process. Ganssle advocates for measuring metrics like bug rates and lines of code to benchmark performance, and critiques the misuse of Linux in deeply embedded systems and the confusion between the maker movement and professional engineering.

Most relevant to

established companies

Topics

Mentioned

Companies
Toyota
Products
Arduino
Chips
ARM Cortex-M
Tools
LDRA
Also
Jack Ganssle, Michael Barr, FDA, FAA, James Grenning, Spark, Ada, Linux, Circuit Cellar, Embedded Systems Dictionary, The Art of Designing Embedded Systems

Related episodes from other shows

Other shows on the same ground, closest first.

  • The Pragmatic Embedded Podcast · 39m

    Christmas Special

    Hosts Jeff Gable and Luca share war stories from their careers in embedded systems, highlighting the pain of manual testing in helicopter avionics, the chaos of managing requirements with Word and Excel in Dropbox for medical devices, and the technical debt of massive #ifdef blocks in legacy machine tool software. They discuss the industry's slow adoption of modern software practices like version control and CI/CD, contrasting embedded development with web development standards. The episode concludes with book recommendations including 'The Phoenix Project' and 'Team Topologies', and reflections on the future of IoT security and agile adoption in hardware.

    Debugging & failure analysisEmbedded firmware
    6 chapters

  • The Amp Hour · 1h 08m

    An Interview with Jack Ganssle (2nd)

    Jack Ganssle, author of the Embedded Muse, discusses the evolution of embedded firmware, highlighting the shift toward cloud-connected platforms and the acquisition of RTOS providers like FreeRTOS by Amazon and ExpressLogic by Microsoft. He critiques the current state of vendor-supplied software, praising Renesas' Synergy platform for providing fully tested, guaranteed software components, while noting the decline of legacy RTOSs like VxWorks. Ganssle emphasizes that firmware development requires rigorous design and quality processes, arguing that jumping into code without solid requirements leads to catastrophic failures, as seen in recent medical device and aviation incidents.

    Embedded firmwareMicrocontrollers & dev platforms
    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 Pragmatic Embedded Podcast · 38m

    The Matthew Test with Matthew Eshleman - Part 1

    Matthew Eshleman, a principal embedded software engineer and consultant formerly at Toshiba, joins Jeff Gable and Luca to discuss his 'Matthew Test,' a 15-step checklist for evaluating embedded software teams. Modeled after Joel Spolsky's Joel Test, the episode covers foundational practices such as using source control (specifically Git), automating build and release processes, and implementing continuous integration. Eshleman argues that unlike web development, embedded engineering requires 'reasonably complete specifications' and early risk management due to the high cost and long lifecycle of hardware changes.

    Embedded firmwareEDA & CAD tools
    6 chapters

  • The Pragmatic Embedded Podcast · 40m

    Does DevOps Make Sense for Embedded Systems?

    Jeff Gable and Luca Engeni discuss why DevOps and Agile principles are essential for embedded systems, particularly in safety-critical industries like medical devices and aerospace. They argue that while hardware iteration is slower than software, fixed cadences for PCB releases can still accelerate feedback loops. The conversation highlights the shift toward over-the-air updates, using Tesla as a case study for the new safety challenges introduced by connected vehicles.

    Embedded firmwareValidation & product-market fit
    6 chapters

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