0:0017:03

Software to Hardware: Two Sides of the Same Coin?

Valentina Ratner 17:03 2023

Hardware teams now move three times faster with the same old tools

Hardware products that once took five years to reach market now ship in 12 to 24 months, yet many teams still pass designs around as PDFs, spreadsheets and email threads. Valentina Ratner, co-founder and CEO of AllSpice.io and a former Amazon PM, sees that gap as costly, because a single wrong board revision can mean anything from rework to a new factory. Which software habits can hardware teams borrow, and which ones break?

See how Git, design reviews and early automated tests translate from software into hardware work

Watch on YouTube

In short

Valentina Ratner, co-founder and CEO of AllSpice.io, argues that hardware engineering is following the path software took: first revision control, then collaboration, then automation. She explains why faster prototyping has outgrown legacy hardware tools, how Git-style workflows and design reviews translate across disciplines, and where hardware differs, from visual data to the far higher cost of mistakes.

“And nowadays they have to do things 3x as fast, but they have the same tools to do so than they did when things took longer.”
“The cost of an error in hardware is exponentially higher because we're talking about physical and real world manufacturing.”

What you will learn

  • Explain why shorter hardware product cycles expose the limits of legacy data management tools.
  • Map software practices such as pull requests, commits, diffs and CI/CD to their hardware design review equivalents.
  • Spot error-prone handoffs between electrical, mechanical, firmware and operations teams.
  • Plan to shift hardware tests from the end of the design process to the beginning.
  • Weigh the higher cost of hardware mistakes when bringing agile practices into physical product development.

Key takeaways from the speaker

  • Gain a deeper understanding of the relationship between software and hardware engineering.
  • See how cross-disciplinary innovation is shaping the hardware industry.
  • Learn how applying software principles to hardware design will shape the future of engineering.

Details

Level
Beginner
Format
Talk
Technical depth
Introductory technical
For
Mid-career, Senior individual contributor, People manager
Length
17:03
Published
June 2023

Questions this talk answers

Why do hardware teams need software-style workflows now?

Prototyping has become cheaper and faster, so products reach market in 12 to 24 months with many more iterations. Yet teams still use data management systems built for five-year product cycles.

Why do disconnected tools hurt hardware teams more than software teams?

Software tools connect through APIs without information loss, while hardware information gets reduced to PDFs, email threads and spreadsheets. That forces manual work, such as listing design changes by hand, which is slow and error prone.

What is the biggest difference between software and hardware workflows?

Software developers work in text-based code, while hardware developers work in visual 2D and 3D vector drawings. Hardware mistakes are also far more expensive because they involve physical manufacturing.

How does a software pull request translate to hardware?

It becomes a design review, where inline feedback maps to snippets on drawings, commits map to links to locations, and diffs and CI/CD tests run on visual schematics.

What comes next for hardware development?

Automation: setting up tests at the start of the design process so they run continuously, instead of testing only at the end when changes are hard to make.

About this talk

This presentation explores trends from software that have made their way into hardware engineering and vice versa, focusing on the popular version control system, git, and other notable innovations.

We will examine the factors that have driven this cross-pollination of technologies and how they have impacted the engineering landscape. The presentation will also cover aspects that have yet to carry over, including challenges with scaling, compatibility, and design considerations.

Topics

Related talks

Browse the library