The Changelog: Software Development, Open Source Voices of Oxide (Interview)
21 snips
Sep 26, 2025 
Cliff Biffle, a firmware engineer at Oxide, talks about the intricate processes involved before a CPU powers on, including adopting Rust for greater safety. Dave Pacheco shares insights into the evolution of Oxide’s self-service update system, tackling challenges like non-disruptive updates and safety safeguards. Ben Leonard, Oxide's head of design, discusses his approach to creating a unified design system that enhances both branding and user experience, highlighting how intentional design fosters trust in a competitive market.
AI Snips
Chapters
Transcript
Episode notes
Boot-Time Firmware Origins
- Cliff describes owning low-level firmware work that runs before the main CPU powers on and handles power, clocks, and flash readiness.
- He says he designed the first board himself as an inexpensive prototype before hiring EEs.
Writing-First Engineering Culture
- Oxide's heavy writing culture speeds hiring and interview efficiency by requiring applicants to produce thoughtful docs up front.
- Cliff stresses prototypes first, then docs when you need consensus or wider collaboration.
Discovering Rust In Firmware Work
- Cliff recounts finding Rust while doing firmware at Google and wanting a safer language than C for teams of mixed experience.
- He adopted Rust around 2015 because it matured at the right time for production needs.