馬斯克的第一性原理思考 5 步法: 真正高效解決問題的人,都在遵循下面這套流程。 步驟 1:先質疑需求 不要急著解決問題,先問自己:...

科技曰
438粉絲
699 次觀看·2026年6月16日
It's easy to say simplify, and it's very difficult to do it.
You know, I have this very basic first principles algorithm that I run kind of as like a mantra,
which is to first question the requirements, make the requirements less dumb. The requirements are
always dumb to some degree, so you want to start off by reducing the number of requirements.
And no matter how smart the person is who gave you those requirements, they're still dumb to
some degree. You have to start there, because otherwise you could get the perfect answer to
the wrong question. So try to make the question the least wrong possible. That's what
questioning the requirements means. And then the second thing is try to delete
whatever the step is, the part or the process step. Sounds very obvious, but
people often forget to try deleting it entirely. And if you're not forced to put back at least 10%
of what you delete, you're not deleting enough. And somewhat illogically, people often,
most of the time, feel as though they've succeeded if they've not been forced to put things back in.
But actually they haven't, because they've been overly conservative and have left things in there
that shouldn't be. And only the third thing is try to optimize it or simplify it.
Again, these all sound, I think, very obvious when I say them, but the number of times I've
made these mistakes is more than I care to remember. That's why I have this mantra.
So in fact, I'd say the most common mistake of smart engineers is to optimize a thing that
should not exist. So like you say, you run through the algorithm, basically show up to a problem,
show up to the supercomputer cluster and see the process and ask, can this be deleted?
Yeah, first try to delete it. Yeah.
Yeah, that's not easy to do. No, and actually, what generally makes people uneasy is that you've
got to delete at least some of the things that you delete, you will put back in. But going back
to sort of where our limbic system can steer us wrong is that we tend to remember with sometimes
a jarring level of pain where we deleted something that we subsequently needed.
And so people will remember that one time they forgot to put in this thing three years ago,
and that caused them trouble. And so they overcorrect, and then they put too much stuff
in there and overcomplicate things. So you actually have to say, look, we're deliberately
going to delete more than we should. It's that we're putting at least one in 10 things we're
going to add back in. And I've seen you suggest just that, that something should be deleted,
and you can kind of see the pain. Oh, yeah, absolutely.
Everybody feels a little bit of the pain. Absolutely. And I tell them in advance, like,
yeah, there's some of the things that we delete, we're going to put back in. And people get a
conservative as to never have to put anything back in. You obviously have a lot of stuff that
isn't needed. So you got to overcorrect. This is, I would say, like a cortical override to
a limbic instinct. One of many that probably leads us astray.
Yeah. There's like a step four as well, which is any given thing can be sped up.
However fast you think it can be done, like whatever the speed is being done, it can be
done faster. But you shouldn't speed things up until you've tried to delete it and optimize it,
otherwise you're speeding up something that shouldn't exist as absurd. And then the fifth
thing is to automate it. And I've gone backwards so many times where I've automated something,
sped it up, simplified it, and then deleted it. And I get tired of doing that. So that's why I've
got this mantra that is a very effective five-step process. It works great.
When you've already automated, deleting must be real painful.
Yeah, it's great. It's like, wow, I really wasted a lot of effort there.
I mean, what you've done with the cluster in Memphis is incredible, just in a handful of weeks.
Yeah, it's not working yet, so I don't want to pop the champagne corks.
In fact, I have a call in a few hours with the Memphis team
because we're having some power fluctuation issues.
When you do synchronized training, when you have all these computers where the training is
synchronized to the millisecond level, it's like having an orchestra. And then the orchestra can go
loud to silent very quickly, at sub-second level. And then the electrical system kind of freaks out
about that. If you suddenly see giant shifts, 10, 20 megawatts, several times a second,
this is not what electrical systems are expecting to see.
So that's one of the main things you have to figure out, the cooling, the power,
and then on the software as you go up the stack, how to do the distributed compute, all of that.
Today's problem is dealing with extreme power jitter.
Power jitter.
Yeah.
That's a nice ring to that. So that's, okay. And you stayed up late into the night,
as you often do, there.
Last week, yeah.
Last week.
Yeah, we finally got training going at, oddly enough, roughly 4.20am last Monday.
I try to do, whatever the people at the front lines are doing, I try to do it at least a few
times myself. So connecting fiber optic cables, diagnosing a faulty connection, that tends to be
the limiting factor for large training clusters, is the cabling. So many cables.
Because for a coherent training system where you've got RDMA, remote direct memory access,
the whole thing is like one giant brain. So if you've got any to any connection,
so it's the, any GPU can talk to any GPU out of 100,000. That is a crazy cable layout.
It looks pretty cool.
Yeah.
It's like the human brain, but at a scale that humans can visibly see. It is a good brain.
I mean, the human brain also has a massive amount of the brain tissue is the cables.
Yeah.
So they get the gray matter, which is the computer, and then the
white matter, which is cables. A big percentage of your brain is just cables.
That's what it felt like, walking around in the supercomputer center. It's like,
we're walking around inside the brain. It will one day build a super intelligent,
super, super intelligent,
