Twitxy Saved

GeniusThinking

Verified account This account is verified. Learn more

@GeniusGTX

Celebrate the human genius and uncover who runs the world. Bullish on humanity. Ghostwriter for world class tech/ai founders.
DM for Collab Joined January 2023
78 Following 291K Followers 12K Posts

Latest posts 5

GeniusThinking Verified account @GeniusGTX
Elon Musk delivers a stark prediction about the future of organizations:

"Pure AI, pure robotics corporations or collectives will far outperform any corporations that have humans in the loop."

He uses a historical analogy to explain: "A computer used to be a job that humans had. You would go and get a job as a computer where you would do calculations."

They'd have entire skyscrapers: 20, 30 floors of humans just doing calculations.

"Now, that entire skyscraper of humans doing calculations can be replaced by a laptop with a spreadsheet."

That spreadsheet can do vastly more calculations than an entire building full of human computers.

He continues the analogy: "What if only some of the cells in your spreadsheet were calculated by humans? Actually, that would be much worse than if all of the cells in your spreadsheet were calculated by the computer."

The implication is clear: having humans in the loop creates bottlenecks.

"Really what will happen is the pure AI, pure robotics corporations or collectives will far outperform any corporations that have humans in the loop. And this will happen very quickly."

This doesn't sound doomish to Musk, it's just what he thinks will happen based on efficiency dynamics.

In five or six years, AI will exceed the sum of all human intelligence. If that continues, at some point human intelligence will be less than 1% of all intelligence.

Musk thinks it's difficult to imagine that if humans have 1% of combined intelligence, they'll be in charge of AI.

But what we can do is make sure AI has values that cause intelligence to be propagated into the universe.
1:50
4 replies 13 reposts 79 likes 10K views View on X
GeniusThinking Verified account @GeniusGTX
In 1998, Steve Jobs asked Tim Cook to join Apple.

Tim Cook was a top executive at Compaq and everyone he trusted told him not to do it.

Here he explains why he listened to his intuition and joined Apple:

"I don't think that you're born with a gut. I think you're, the gut matures and gets better and better over time. And what the struggle that most people have, I think, is learning to listen to it and figuring out how to access it in some way.

For me though, what I found was that even though I'm an engineer and an analytical person at heart, the most important decisions I've made had nothing to do with any of that.

They were always based on intuition. And the Apple one is a prime example of that. I remember actually forming my list of pluses and minuses, and I could not get the chart to work out the way I wanted it to.

'Cause I wanted something to say, "This says I should go to Apple." But it would not. There was nothing financially would do that. I talked to people I trusted that knew me and they said, "This is not what you should do."

It wasn't so easy and people said, "You know, you're just crazy. "You're working for the top PC company in the world. "How could you even think of doing this? "You've lost your mind."

And yet, that voice said, "Go west, young man, go west." And sometimes you just have to go for it.
2:47
3 replies 12 reposts 75 likes 29K views View on X
GeniusThinking Verified account @GeniusGTX
Elon Musk explains his 5-step process for running companies:

"First, make your requirements less dumb. Your requirements are definitely dumb. It does not matter who gave them to you.

It's particularly dangerous if a smart person gave you the requirements because you might not question them enough. Everyone's wrong no matter who you are.

Everyone's wrong some of the time. So make your requirements less dumb. Then try very hard to delete the part or process.

This is actually very important. If you're not occasionally adding things back in, you are not deleting enough.

The bias tends to be very strongly towards let's add this part or process step in case we need it. But you can basically make in-case arguments for so many things and for a rocket that is trying to be the first fully reusable rocket.

There's never been a fully reusable rocket. People don't understand. This is like the holy grail of rocketry. So you've got to delete the part or process step. Super important.

You can't hedge your bets. That's why the grid funds, for example, do not fall down because that's a whole extra mechanism that we don't need.

Also, whatever requirement or constraint you have, it must come with a name, not a department. Because you can't ask the department. You have to ask a person. That person who's putting forward their requirement or constraint must agree that they must take responsibility for that requirement.

Otherwise, you can have a requirement that basically an intern two years ago randomly came up with off the cuff and they're not even at the company anymore. These things are often just way more silly than you think. So step one, make your requirements less dumb.

Step two, delete the part or process step. If you're not adding things back in 10% of the time, you're clearly not deleting enough.

And then only the third step is simplify or optimize.

The third step, not the first step. The reason it's the third step is because possibly the most common error of a smart engineer is to optimize a thing that should not exist.

Everyone's been trained in high school and college that you've got to answer the question. Convergent logic. So you can't tell the professor your question is dumb. You'll get a bad grade. You have to answer the question. So everyone's basically, without knowing it, they've got a mental straitjacket on. They'll work on optimizing the thing that should simply not exist.

And then finally, you get to step four, which is accelerate cycle time.

You're moving too slowly, go faster. But don't go faster until you have worked on the other three things first. You can always make things go faster.

And then the final step is automate.

Now, I've personally made the mistake of going backwards on all five steps multiple times. Literally, I automated, accelerated, simplified, and then deleted.

One example I've talked about before is there were these fiberglass mats on top of the Model 3 battery pack that were in between the floor pan and the battery.

And it was at one point choking the battery pack production line. And I was basically living on the battery pack production line trying to fix the line.

It was choking the entire Model 3 production program. So the first mistake was I tried to fix the automation, like make the robot better. So automating was a mistake. Then accelerating was a mistake. Then optimizing was a mistake.

And finally, I said, what the hell are these mats for?

And I asked the battery safety team, what are these mats for? Are they for fire protection or something?

They said, no, they're for noise and vibration. Then I asked an NVH, a noise, vibration, harshness team, what's it for? They said fire safety.

So literally, it was like being in a Dilbert cartoon. Actually, I feel like I'm in a Dilbert cartoon quite frequently. So then finally, OK, great, let's try a car with the fiber glass mats and without. And they put a microphone to both and see if you can tell the difference.

In fact, I was like, which one is which? So we just deleted them and just bypassed this $2 million robot cell.

It was just a complete pile of nonsense."
4:09