You sort of have to separate what are questions you can ask that are going to help make you smarter about your thesis versus... trying to get somebody to validate it for you.

No one is going to tell you what to build. If they did, then they should do it, not you.

It turned out that building mobile software was a lot more like building hardware... where you had 1 shot and you had to get it right, right out of the gate.

You sort of have to separate what are questions you can ask that are going to help make you smarter about your thesis versus... trying to get somebody to validate it for you.

We can dream a lot faster than what's possible.

Everything for us is a system. We don't think about it discretely as just as a piece of hardware, or discretely as an application... or discretely as a platform. We think about it across the whole thing.

I have a daily call thats 2.5 hrs with the entire team: from materials, sourcing, manufacturing, design, sensor, firmware... mechanical engineering - all together and they all have to sit through each other's updates... but then understand what those tradeoffs are and I sort of force that communication.