Hardware Podcasts

413: Puppy-Like Glee

Embedded.fm · 19 May 2022 · 1h 08m · Episode 413

What this episode covers

Elecia White and Christopher White discuss the psychology of self-directed learning, using Christopher's drum practice and Elecia's embedded systems teaching as parallel examples. They debate the practical application of software quality practices, arguing that compiler warnings and linters are essential for catching errors, while unit tests and complexity metrics must be applied with context and risk assessment. The conversation concludes with advice on managing unmotivated team members, emphasizing empathy, communication, and understanding external constraints over assuming incompetence or malice.

Most relevant to

early-stage companies

Topics

Mentioned

Products
Fitbit
Tools
Clang, PC-lint
Also
Classpert, Contextual Electronics, LeetCode, TensorFlow

Related episodes from other shows

Other shows on the same ground, closest first.

  • The Pragmatic Embedded Podcast · 1h 23m

    Crossover with Elecia White and Christopher White of Embedded

    Elecia White and Christopher White of Embedded.fm join Jeff Gable and Luca Ingiani to discuss applying agile principles to embedded systems, emphasizing risk management and fast feedback loops over rigid methodologies. They debate the definitions of Minimum Viable Products (MVPs) and prototypes, noting that while software allows for rapid iteration, physical products require careful consideration of shelf-life and Bill of Materials (BOM) costs. The group also addresses the practical challenges of unit testing in embedded development, suggesting it be reserved for high-risk, high-churn code rather than stable drivers, and discusses how to pitch agile concepts to skeptical managers by focusing on risk reduction rather than process dogma.

    Embedded firmwareValidation & product-market fit
    10 chapters

  • The Pragmatic Embedded Podcast · 53m

    Terrible Habits of the Solo Developer

    Jeff Gable and Luca Jani, both solo embedded software consultants, discuss the unique challenges of working alone, such as multitasking pressure and wearing multiple hats. They identify five bad habits: skipping documentation, avoiding code reviews, making poor architectural decisions, neglecting simulators, and failing to make code easy for others to take over. The hosts propose solutions including hiring third-party reviewers, using LLMs for low-level checks, forming mastermind groups, and enforcing self-imposed processes to maintain quality and sanity.

    Embedded firmwareCareers & education
    12 chapters

  • 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 Pragmatic Embedded Podcast · 36m

    Development is Better when it's Test-Driven

    Jeff Gable, an embedded software consultant, explains his practice of Test-Driven Development (TDD) to host Luca Ingianni, arguing that writing failing unit tests before application code forces good architecture and high coverage. Gable details how this discipline decouples embedded application logic from hardware-specific drivers, allowing tests to run on the host machine for rapid feedback rather than slow target flashing. He addresses the common industry resistance to TDD in embedded systems, citing the initial learning curve and the need for coaching, while recommending resources like the 'Throw the Switch' video courses and tools such as Unity, CMock, and Ceedling. The conversation concludes by framing TDD as an artistic craft of storytelling through code, emphasizing that the practice builds confidence and prevents regressions in production-quality software.

    Embedded firmwareDebugging & failure analysis
    9 chapters

  • The Pragmatic Embedded Podcast · 42m

    Code Reviews

    Jeff Gable and Luca discuss the purpose, process, and culture of code reviews in embedded software development. They argue that reviews are primarily for knowledge transfer, shared understanding, and mentoring rather than just bug detection, warning against 'bike shedding' on trivial syntax issues. The hosts advocate for early design reviews, small atomic commits, and empathetic communication to maintain team cohesion and prevent bottlenecks.

    Careers & educationLeadership, teams & culture
    7 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.