Nimendra's Notes 🪴

The Book of Elon

3 min read

books booknotes biography productivity

Tldr

Eric Jorgenson — The Book of Elon

Scribe Media, 2026 · 386 pages · ISBN 9781544550749

A distilled collection of Elon Musk’s principles on first-principles thinking, extreme execution, communication, and management. The recurring themes: delete the unnecessary, punish nothing, aim at reality, and work on the problems that matter.

Thinking

  • History doesn’t repeat, but it does rhyme — and reading history is how you catch the rhyme. “I try to understand the rise and fall of civilizations. I’ve read a lot of history to discern the facts of what humans did.”
  • If everyone is thinking about exactly the same things the same way, that may not create new knowledge.
  • You can teach yourself anything. Read widely; talk to experts.
  • On the big stakes: “The birth rate might be the biggest single threat to the future of human civilization. AI gone wrong is a big concern. Religious extremism is a concern. There are quite a few important problems to solve.”

Execution

  • You must be extremely tenacious. Work like hell. You have to put in eighty- to one-hundred-hour weeks every week. This will improve your odds of success.
  • “I don’t care about optimism or pessimism. Fuck that. We’re going to get it done.”
  • Do things in parallel.

On being liked

I think it’s a real weakness to want to be liked. A real weakness. And I do not have that.

Communication

  • Don’t use acronyms or nonsense words for objects, software, or processes. In general, anything that requires an explanation inhibits communication. We don’t want people to have to memorize a glossary just to function.
  • The most simple, straightforward, low-ego terms are generally best. You want to close the loop on reality hard.

First principles of simplification

The ordering

  1. Make your requirements less dumb
  2. Try very hard to delete the part or process
  3. Simplify or optimize
  4. Accelerate
  5. Automate

The engineer's trap

The most common mistake of smart engineers is to optimize a thing that should not exist.

Everyone was trained in high school and college to answer the question in front of them — it’s convergent logic. You can’t tell the professor, “Your question is dumb.” Without knowing it, almost everyone has this mental straightjacket on. They’ll work on optimizing a thing that should simply not exist.

Less stuff, less process

  • The best part is no part. The best process is no process.
  • It’s easy to say “simplify,” but it’s very difficult to do it.

Management

  • If you punish people too much for failure, then they will respond accordingly, and the innovation you get will be incremental. Nobody’s going to try anything bold for fear of getting fired or being punished in some way. If you expect innovation, the compensation structure must reflect that.
  • On hardware reality: prototypes are easy and fun. Reaching volume production with a reliable product at an affordable price is excruciatingly difficult.
  • The first goal is to make the damn thing work — we’ll optimize it later.

Selected highlights

“The most common mistake of smart engineers is to optimize a thing that should not exist.”

“The best part is no part. The best process is no process.”

“If everyone is thinking about exactly the same things the same way, that may not create new knowledge.”

“You can teach yourself anything. Read widely; talk to experts.”

Graph View