Artwork

Content provided by MacroFab, Inc.. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by MacroFab, Inc. or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

EP#415: CI/CD - We Salute You with Brenden Duncombe

45:41
 
Share
 

Manage episode 398319475 series 120573
Content provided by MacroFab, Inc.. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by MacroFab, Inc. or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

This week Parker and Stephen welcome Brenden Duncombe to the show to discuss the pros and cons of continuous integration and continuous delivery/deployment (aka CI/CD) for hardware. Continuous integration (CI) refers to the practice of automatically and frequently integrating code changes into a shared source code repository. Continuous delivery and/or deployment (CD) is a two-part process that refers to the integration, testing, and delivery of code changes. In theory, CI/CD helps organizations avoid bugs and code failures while maintaining a continuous cycle of software development and updates, but we wanted to learn more about this with Brenden, so Parker and Stephen asked him about CI/CD, and also covered the following:

  • Brenden’s product development background
  • “What is a Director of Customer Engineering?”
  • A brief history of CI/CD
  • Why it’s the opposite of a nightmare
  • Unit tests for software…how does it work for hardware?
  • Pinball Wizardry
  • A “smearing” vs. a “silo”
  • Test-driven dev benefits over the entire dev cycle
  • Is CI/CD a hard concept to sell?
  • How to make the investment worthwhile
  • The Hardware Regression Struggle
  • When start-ups aren’t really prepared for contract manufacturers
  • What is the ideal development cycle?
  • Building something for your contract manufacturer? Always build two
  • Teenage Engineering
  • Prep your firmware people with dev boards before the hardware reaches them
  • “Like taking your specification doc and writing a test doc on top of that”
  • Standard Fixtures and Future MacroFab Projects
  • + more!

About our guest:

Brenden Duncombe is the Director of Customer Engineering at MacroFab. His extensive experience in Electrical and Systems Engineering, and his leadership in steering engineering teams from concept to manufacturing, make him an essential voice at Macrofab.

Relevant links:

Thank you for listening to the MacroFab Engineering Podcast! We’d love to hear what you think of the show so please tweet at us @MacroFab and join our Circuit Break Community for discussions or email us at [email protected].

  continue reading

448 episodes

Artwork
iconShare
 
Manage episode 398319475 series 120573
Content provided by MacroFab, Inc.. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by MacroFab, Inc. or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

This week Parker and Stephen welcome Brenden Duncombe to the show to discuss the pros and cons of continuous integration and continuous delivery/deployment (aka CI/CD) for hardware. Continuous integration (CI) refers to the practice of automatically and frequently integrating code changes into a shared source code repository. Continuous delivery and/or deployment (CD) is a two-part process that refers to the integration, testing, and delivery of code changes. In theory, CI/CD helps organizations avoid bugs and code failures while maintaining a continuous cycle of software development and updates, but we wanted to learn more about this with Brenden, so Parker and Stephen asked him about CI/CD, and also covered the following:

  • Brenden’s product development background
  • “What is a Director of Customer Engineering?”
  • A brief history of CI/CD
  • Why it’s the opposite of a nightmare
  • Unit tests for software…how does it work for hardware?
  • Pinball Wizardry
  • A “smearing” vs. a “silo”
  • Test-driven dev benefits over the entire dev cycle
  • Is CI/CD a hard concept to sell?
  • How to make the investment worthwhile
  • The Hardware Regression Struggle
  • When start-ups aren’t really prepared for contract manufacturers
  • What is the ideal development cycle?
  • Building something for your contract manufacturer? Always build two
  • Teenage Engineering
  • Prep your firmware people with dev boards before the hardware reaches them
  • “Like taking your specification doc and writing a test doc on top of that”
  • Standard Fixtures and Future MacroFab Projects
  • + more!

About our guest:

Brenden Duncombe is the Director of Customer Engineering at MacroFab. His extensive experience in Electrical and Systems Engineering, and his leadership in steering engineering teams from concept to manufacturing, make him an essential voice at Macrofab.

Relevant links:

Thank you for listening to the MacroFab Engineering Podcast! We’d love to hear what you think of the show so please tweet at us @MacroFab and join our Circuit Break Community for discussions or email us at [email protected].

  continue reading

448 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide

Copyright 2025 | Privacy Policy | Terms of Service | | Copyright
Listen to this show while you explore
Play