Jessica Livingston

20 years ago there was a building in SF that was nicknamed the Y Scraper because so many YC founders lived there. They just had a reunion and it makes me so happy to see them all. One thing you can say for sure about YC: no investor's founders become closer friends.

12 years ago I founded Boom, as a software engineer doing hardware for the first time. I’m probably the least handy founder in hard tech. My 12 y/o son does my soldering and 3D printing for home projects, and I’ve struggled with imposter syndrome the whole way through. What business does a software guy have building supersonic jets and turbines? More than a decade in, the most insane realization is that software is the key to reaccelerating hardware engineering. But in a way that I don’t think is widely understood or implemented, even in the burgeoning hard tech community. Most hardware engineering is actually software engineering in disguise. It’s spreadsheet “code,” engineering calculations done as one-offs. Eg wing structural loads in, spar sizing design out. Thermal loads in, air conditioning system sizing out. Everything is a calculation, and calculation is software. But these calculations are done essentially by hand, as if we are doing arithmetic but have not yet discovered algebra. Hardware engineers have baby software, built in spreadsheets, the kind of crappy software I wrote as a kid before I understood architecture, unit tests, APIs, version control, and everything else that makes modern software good. Our airplanes and engines are built with the software sophistication of a script kiddie. So what we tell our engineers: don’t design the hardware, design the *algorithm* for designing the hardware. And take the algorithm seriously—as an algorithm and as a first-class engineered software system. Never design a piece of hardware, such that you couldn’t redesign it tomorrow with a different set of assumptions. This all sounds obvious, yet our experience at Boom is that it changes everything. Ten years ago we couldn’t afford to build much software. We had a small team—and there were few software engineers with the curiosity, brilliance, and vision required to learn hardware engineering. But now AI changes the equation. Now everyone can code. The software engineers define the architecture. The hardware people bring the physics and engineering know-how. We have a turbomachinery design tool that lets one engineer do in realtime what previously took 100 engineers six months. Another tool auto-generates 65% of entire aircraft structure. I’m sure we’ll figure out the other 35% too. Eventually these should not be multiple tools, but one integrated physics model of a complete vehicle, airframe and powertrain. The results speak for themselves. A boomless supersonic airplane built by 50. A full scale supersonic turbine made by 150. And with this approach, I don’t think we’ll need that many more people to build and certify a supersonic airliner. You don’t need a big team to build big things—not when everyone on the team is a software engineer.

I’m speaking at a shipping industry conference today and the hosts asked my team for confirmation that I won’t criticize their sponsors. A Flexport marketing team member accidentally responded “Ryan will definitely criticize the other sponsors” 🍿🍿🍿

can I use this as a blurb for the book?

Meeting with my archnemesis @Suhail We spent 10 years battling it out in analytics between Amplitude and Mixpanel. Surprisingly, we have much more in common than expected. I’m learning marketing from him and he’s learning sales from me.

All I want for Christmas is to hear The Social Radars and @TylerShultz_ debrief You Can See Everything

With the Man, Ron Conway.