potato face
CryingPotato

#reading

A Tale of Two Biographies #

As part of my most recent reading strategy I’ve been reading a lot of biographies. I finished the Power Broker in early April, and started reading Isaacson’s biography about Elon Musk more recently. I’d heard excellent reviews about the latter, but halfway through it, I’m sorely disappointed.

What strikes you when reading the Power Broker is the depth of research, the coherence of story and the intensity of feeling that Robert Caro has managed to put into words. None of these exist with the Musk biography. Chapters are short, out of chronological order and feel woefully under written and under researched. For example:

(Chapter 35: Marrying Talulah) … It’s actually funnier than I made it sound …

Why not just make it sound.. funnier? I’m not saying it’s easy, but its definitely something I’d have expected of Isaacson.

(Chapter 6: Canada: 1989) … most jobs paid $5 an hour. But there was one that paid $18 an hour, (… describes job).

Did he take the job? We never find out. Presumably yes, based on the description, but it was ambiguous enough while reading it that it stood out to me.

Setting aside individual nits, the biggest disappointment is how uninteresting the story feels (despite how interesting the story actually is). When I read Jobs, I was much more motivated to find out what happens next. Here, it’s as though I’m reading through an extended Wikipedia entry.

Admittedly, I am only halfway through the book, but I am skeptical that the style of writing changes significantly in the latter half of the book. Perhaps this is too harsh of a review, and my biography fatigue might be partly to blame for it, but there’s definitely something missing in this book.

How Big Things Get Done: A Reading Strategy #

The focus of this reading strategy is “How Big Things Get Done” - both on an individual and an organizational level. Like with my previous reading strategy, the first rule was to come up with a simple list of questions to answer:

  • How hard vs. smart did people who got big things done work?
  • Were most of them innately smart, or was there something else? What subsets of traits did a lot of them share?
  • How did they interact with other people?
  • Did they go wide or deep?
  • What were values they had? What values did they share?
  • What were key organizational principles to getting people to work together on large projects?
  • How large/ unrealistic were the visions of big projects when they started? Did they have to tone it down, or did they just achieve it?
  • What were key reasons large projects failed?

This is a fairly broad category and I don’t expect to get definitive answers to everything here. Again, as before, I have a curriculum of books. This being a fairly wide topic, the books are also fairly wide (and a bit random), but the benefit of that is I’ve already read quite a few of them (marked with ✓)

  • How Big Things Get Done
  • The NASA paper on why Apollo was a success
  • The Art of Doing Science and Engineering (reread You and Your Research) ✓
  • Read technical plans for {insert major project here}
  • Biographies/ history of people who got “big things done”
    • A Mind At Play (Claude Shannon) ✓
    • Elon Musk biography
    • Creativity Inc. ✓
    • The Power Broker
    • Read Founders (on Paypal founders)?
    • Jon Von Neumann ?
    • Masters of Doom ✓
    • Jobs ?

Reading With Intent #

It’s always been easy for me to “get through” reading. You simply skim through the page, absorb a part of the material, and fumble your way around deep understanding, instead substituting it with words that sound like intelligence.

This is obviously a terrible strategy for deeply understanding anything, and many things have recently taught me that. One example was going through Reflections on Trusting Trust recently. Ken Thompson talks about quines early on, saying:

If you have never done this, I urge you to try it on your own.

Past me would have skimmed through for an answer, but now I opened up a terminal. The best I could come up with myself after 20 minutes was

with open('main.py') as f:
	print(''.join(f.readlines()))

On researching quines after this, I discovered that I had “cheated” by reading the file. When going through this I finally understood how one could produce a quine in Python: the key was understanding that repr prints the string with quotes. Writing partially from memory now:

data = ";print('data = ' + repr(data) + data)";print('data = ' + repr(data) + data)

Books of 2023 #

I wanted to write a full review of a lot of books I read this year, but I ran out of time. So instead, here’s a quick little rating scale out of 5 🥔s. It’s also in the rough order I read them this year. If anything is below 3 🥔s, definitely just read a summary. 3/4 is up to your judgement, please read every 5 🥔.

BookRatingCategory
Pieces of
the Action
🥔🥔🥔History
Where is My
Flying Car
🥔Rant
Learning to Learn🥔🥔🥔Science
Forest of Enchantments🥔🥔🥔🥔Drama
Dune🥔🥔🥔🥔Sci-fi
Dune: Messiah🥔🥔🥔Sci-fi
Children of Dune🥔🥔🥔🥔🥔Sci-fi
God Emperor
of Dune
🥔🥔🥔🥔Sci-fi
Creativity Inc.🥔🥔🥔🥔🥔Biography
The Betrayed Wife🥔🥔🥔Thrilled/ Mystery
Born to be
Hanged
🥔🥔🥔🥔🥔History
Tomorrow & Tomorrow &
Tomorrow
🥔🥔🥔🥔🥔Drama
Masters of Doom🥔🥔🥔🥔History
Thinking in Systems🥔🥔🥔Systems?
Atlas Shrugged🥔🥔🥔Drama
Six of Crows🥔🥔🥔🥔Sci-fi