Jensen Huang

And so that's a good frame of mind.

I don't love the other methods, which is continuous improvement.

The problem with continuous improvement,

first of all, you should engineer something from first principles at the speed, you know, with speed of light thinking limited only by physical limits and, and physics limits.

And, um, after that, of course you would improve it over time.

Um,

But I don't like going into a problem and somebody says, hey, it takes 74 days to do this today, right now, and we can do it for you in 72 days.

I'd rather strip it all back to zero and say, first of all, explain to me why 74 days in the first place.

Let's think about what's possible today.

If I were to build it completely from scratch, how long would it take?

Oftentimes, you'd be surprised and might come to six days.

Now the rest of the six days to 74 could be very well reasoned and compromises and cost reductions and all kinds of different things, but at least you know what they are.

And now that you know that six days is possible, then the conversation from 74 to 6 is surprisingly much more effective.

And Lex, we'll probably kind of crank out about 200 of these pods a week, just to put in perspective.

You know, the phrase that I use most often is we need things to be as complex as necessary, but as simple as possible.

And so the question is, is all that complexity there necessary?

And we ought to test for that.

And we ought to challenge that.

And then after that, everything else above it, you know, is gratuitous.

It is the most complex computer the world has ever made.