z životopisu: "algoritmus", který musk požaduje po inženýrech a neustále ho opakuje. requirement = "někdo to tak chtěl"
The algorithm
At any given production meeting, whether at Tesla or SpaceX, there is a nontrivial chance that Musk will intone, like a mantra, what he calls “the algorithm.” It was shaped by the lessons he learned during the production hell surges at the Nevada and Fremont factories. His executives sometimes move their lips and mouth the words, like they would chant the liturgy along with their priest. “I became a broken record on the algorithm,” Musk says. “But I think it’s helpful to say it to an annoying degree.” It had five commandments:
1. Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so, even if the requirement came from me. Then make the requirements less dumb.
2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough.
3. Simplify and optimize. This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist.
4. Accelerate cycle time. Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted.
5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out.
The algorithm was sometimes accompanied by a few corollaries, among them:
All technical managers must have hands-on experience. For example, managers of software teams must spend at least 20% of their time coding. Solar roof managers must spend time on the roofs doing installations. Otherwise, they are like a cavalry leader who can’t ride a horse or a general who can’t use a sword.
Comradery is dangerous. It makes it hard for people to challenge each other’s work. There is a tendency to not want to throw a colleague under the bus. That needs to be avoided.
It’s OK to be wrong. Just don’t be confident and wrong.
Never ask your troops to do something you’re not willing to do.
Whenever there are problems to solve, don’t just meet with your managers. Do a skip level, where you meet with the level right below your managers.
When hiring, look for people with the right attitude. Skills can be taught. Attitude changes require a brain transplant.
A maniacal sense of urgency is our operating principle.
The only rules are the ones dictated by the laws of physics. Everything else is a recommendation.
==
co se tyce algoritmu, zajimalo by me, jestli nekdy dojde ke kopernikovskemu obratu, kdy by Musk zacal vnimat sam sebe jako soucast procesu a zacal optimalizovat sebe. nevim kolik bere toho ketaminu .. o psychedelikach se kniha nezminuje. je tam jen jedna zminka kdy Kimbal chtel aby si na covid dali ayahuascu, ale musk nechtel: Elon declined. “I’ve just got emotions buried under so much layers of concrete, I’m just not ready to open that up,” ale tak nikdy neni pozde :) tak uvidime.