Загрузка видео...

Не удалось загрузить видео

На главную

🚀 What if the exact same 5-step algorithm Elon uses to build Starships and revolutionize manufacturing could completely transform how you approach challenges in your own life? In this powerful clip from @EverydayAstronaut’s unforgettable Starbase tour with Elon Musk, he walks through his legendary process in detail — question...

13,734 просмотров • 2 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Elon Musk explains his 5-step algorithm for solving any problem: "The most common mistake of smart engineers is to optimize a thing that should not exist." "I have this very basic first principles algorithm that I run as a mantra." Elon breaks it down: Step 1: Question the requirements. "Make the requirements less dumb. The requirements are always dumb to some degree, no matter how smart the person who gave you those requirements. You have to start there, because otherwise you could get the perfect answer to the wrong question." Step 2: Try to delete it. "Try to delete the part or the process step entirely. If you're not forced to put back at least 10% of what you delete, you're not deleting enough. Most people feel like they've succeeded if they haven't been forced to put things back in. But actually they haven't, they've been overly conservative and left things in that shouldn't be there." Step 3: Optimize or simplify. "The most common mistake of smart engineers is to optimize a thing that should not exist. So you don't optimize until after you've tried to delete." Step 4: Speed it up. "Any given thing can be done faster than you think. 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." Step 5: Automate. "And then the fifth thing is to automate it." Elon explains why the order matters: "I've gone backwards so many times where I've automated something, sped it up, simplified it, and then deleted it. I got tired of doing that. So that's why I have this mantra."

Jaynit

384,693 просмотров • 27 дней назад

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 fiberglass 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."

Founder Mode

74,187 просмотров • 5 месяцев назад

we all dream of those big wins in life the 100x, the multi-million dollar trade, or even just 10x of what you started with in 7 days i’ve been fortunate enough to experience a few of those over the past few years, and the reality is when you do win big, it doesn’t feel like it at all it hits for a split second, and then your brain just normalizes it it's a part of how to get there in the first place, but makes it a lot easier to lose it if you don't have the right guardrails in place and in that exact moment, you being even keeled doesn’t mean the number in front of you isn’t life changing it is this is where you have to slow down a bit, breathe, settle your mind don’t just roll it into some bullshit take some off the table, step away for a few days if you have to, funny enough, blowing let's say 10k of it on a beautiful trip to tokyo will save you so much because once you actually process what just happened, your future self will thank you for it the truth is, even if you think you’re going for a certain number, the moment you hit it, you’ll want more and more, and more anyone who's been in the same position will tell you the exact same thing ironically the people that win are addicted to winning and if you ask the same people in a year after that big win, what they regret and where are they proud of themselves? they will tell you they regretted rolling it over and giving some/all back or they are proud for switching back on the switch all of this is real, but it’s also exactly how i imagined it would feel years ago before it ever happened manifest your life, the feeling not just the number everything happens twice, first in your mind, then in reality

۟

23,017 просмотров • 4 месяцев назад

Q: Why is company culture important? In the clip below, a16z cofounder Ben Horowitz argues that culture drives how people in your company behave on a daily basis—and particularly, how they behave when you’re not looking. Is that phone call so important I need to return it today or can it wait until tomorrow? Can I ask for a raise before my annual review? Is the quality of this document good enough or should I keep working on it? Do I have to be on time for that meeting? Should I stay at the Four Seasons or the Red Roof Inn? Should I go home at 5 p.m. or 8 p.m.? Should we discuss the color of this new product for five minutes or thirty hours? If I know something is badly broken in the company, should I say something? Whom should I tell? Is winning more important than ethics? None of these things are in your mission statement or OKRs, but they determine many important things for your company, such as how people experience your company, what you’re like to do business with, what your company is like to work at, etc. And as Ben describes, what drives the culture is all of the little behaviors and cues people take on: “this is what I have to do to succeed in this company.” Culture can feel abstract and secondary when you pit it against a concrete result that’s right in front of you, but it’s a strategic investment in the company doing things the right way when you are not looking. It’s the set of assumptions your employees use to resolve the problems they face every day. It’s how they behave when no one is looking. If you don’t methodically set your culture, then two-thirds of it will end up being accidental, and the rest will be a mistake. If you’re looking for a more in-depth guide to culture and how to build a great one, I’d recommend Ben’s book: What You Do Is Who You Are.

Michael McGuiness

180,646 просмотров • 3 лет назад