I’ve been reading a lot of things that are just compilations of links lately, like Benedict Evans’ newsletter and SSC links posts, and I’m inclined to start my own, partly so I can start posting regularly again. I’ll try to do this every week. It’ll mostly be stuff I found interesting the past week.

From SSC: Two basic at-odds political meta-theories: conflict theory vs. mistake theory. Conflicts theorists view politics as a zero-sum game, where it’s a constant struggle between those with power and those without. Poor political decisions are poor because they benefit the oppressive class. Mistake theorists think poor decisions come from poor decision-making/priors instead of power struggles.

The original rsync paper is surprisingly short, easy to read, and elegant.

A very good list of 57 startup lessons from the founder of RethinkDB. It’s hard to pick a favorite, but I’ll try:

Minimize complexity. The simpler the product, the more likely you are to actually ship it, and the more likely you are to fix problems quickly.

An oldie but a goodie: Steve Yegge’s Platforms Rant. Illustrates the importance of having a platform. You can’t expect to consistently build what users want. Let other developers do the work for you by building a platform instead and opening it up. AWS and Zynga-era Facebook games are great examples of this. So was Twitter before they added developer restrictions.

Why does SF have a huge homeless problem? Here’s why: 1) Insane rents due to NIMBYism, 2) Easy weather (you won’t see too many homeless in Montreal), and 3) Mental illness, although this may be circular: becoming homeless for an extended period of time probably makes you go crazy.

50 insane icebreaker questions by Chuck Klosterman: my favorite is Canadian Football Future — reminds me of DFW for some reason.

A $1.50 Michelin Star meal in Singapore. Particularly relevant cause I’m in Singapore right now and I really want to go try this place out, but it’s raining pretty hard right now. Maybe tomorrow.

Shameless self-promotion: I wrote a post on backtracking.

I used Elm to create the visualization. It was such a pleasure to use — like Haskell, but more front-end oriented. Here’s a good beginner’s book on Elm.

What I’m listening to this week: