I think that 'system think' is a mindset.

You have to take those concepts and prove them, a little bit like you do a PhD thesis.

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

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.

In the hardware world, you've got to take your time because your iteration cycles are much more deliberate.

You have to have the definition of what you're trying to do across the system.

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.