There they played Elon’s favorite new video-game obsession, Polytopia, and binge-watched Cobra Kai, a Netflix series based on the Karate Kid movie.”
— Elon Musk by Walter Isaacson
This was particularly pronounced when Bezos bought the Washington Post. When the paper contacted Musk about a story it was reporting in 2021, he sent an email that simply said, “Give my regards to your puppet master.”
— Elon Musk by Walter Isaacson
Ozempic
The Algorithm
- 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.
- 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.
- 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.
- 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.
- 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.
— Elon Musk
Hearing his French accent, I realized he was the same Ben—Ben San Souci—who had asked Musk about content moderation at the coffee-bar visit. An engineer by demeanor, he wasn’t a natural networker, but he was suddenly being swept into the inner circle. It was a testament to the value of serendipity—and of showing up in person.
— Elon Musk
Serendipity: the occurrence and development of events by chance in a happy or beneficial way.
A serendipity is an unplanned fortunate discovery. They are common occurrences throughout the history of product invention and scientific discovery.
— https://en.wikipedia.org/wiki/Serendipity
I share my feeling with Linus about how noisy Twitter is, and how it is not designed to record thoughts, which I may want to occasionally share, but have no mean to get other people's thoughts on.
Why don't you just use Twitter, then? I hear you asking. I could, but there are a few problems with Twitter. First, Twitter is extremely noisy. There's a million other people vying for your attention next to what I have to say. Twitter is also quite limiting, not just in the character count, but also in that they only let you write in plain text, without any formatting unless you resort to ugly Unicode hacks. Lastly, Twitter is great for "in the moment" discussion in public, but it's not so great as a reference you can link to from the future, and as a historical record of my thinking and work. I wanted a place more purpose-built, more focused, and more permanent for my less permanent thoughts and updates.
That's the reason why I set up this stream instance.
Hello World.