The ARPA Model isn't what you think it is

Engineering organizations today have ballooned to huge numbers of people, but these huge engineering organizations don’t exactly have a reputation for high velocity output. Some of this is the result of what happens with products at scale: it is just fundamentally faster and easier to iterate, improve, or change a product with 100 users than it is ... See more

This is not generally how we run collaborative systems because we run them by consensus, which is the exact opposite. That's about pruning out stepping stones. People start generating things and then we start saying, "No, no, no. Committee doesn't like this. Committee doesn't like that." We then converge to the thing, which is basically the consens... See more

Many concepts that sound good on paper are infeasible to implement, or simply don’t produce the expected results. It’s frustrating when that happens, of course, but the pace of experimentation and learning at a startup is unparalleled. I think this is an especially important form of rigor for theorycels like me. Building product forces a different ... See more

at an institution, you can’t just do what is best, you also have to build trust and coordinate with others so you are on the same page. This, however, doesn’t mean that you should abdicate your judgment and get in line.

I like the approach Sholto Douglas expressed in his interview with Dwarkesh Patel:

If I’m trying to write some code and something is

... See more