How to Design for Optimization
Hey All, so I often transcribe sections I like from audiobooks, blogs, podcasts etc. and save them for later. I saved this excerpt without reference two years ago, and now I'm trying to find where it's from. It references leading VC's in Silicon Valley, so it's definitely 2005+.

_______________

Maybe I’m affected by me growing up in an an unprecedented part of history, where the entire human knowledge is available through the click of a button. This has a number of key implications.
The first, If you fail, it’s hard to blame anyone but yourself. This is because unless you’re working on something truly unique, which is improbable, someone has worked on it before, and you can learn from that person. It’s true that the unique circumstances of the situation can be specific to you, but in general, most of the cases we deal with in life are some form of variation, of not outwright exactly the same, to something that someone else had dealt with before.

The second. The main problem in for most of history was to acquire the information necessary to gain the knowledge (we can think of knowledge as applied information, analagous to how engineering is applied sciences). For the first time ever, the problem isn’t getting the information; it’s all there on your browser, but it’s finding credible sources where the information is reliable, clear, and relevant to your situation. This is hard, and often takes skills. But you can often find those skills by going down the knowledges pipeline.

First, ask, who would know how to get such an information?

A librarian would likely have the formal education to go through the process of finding information. This means you can learn a lot from them. talk to a librarian, or find an online library, and read through their guidelines and processes. If this doesn’t get you through the process of finding information, it will at minimum throw you into the general community where there is applied knowledge on this, and you can begin to navigate to secondary sources.

Second, ask, who has gone through this before?

It is extremely improbable that no one had gone through what you’re through before. If you’re a startup founder and are confused about how to raise funds for the first time, figure out who has gone through that process before? probably other founders of bigger organizations. Talk/email them, and figure out how they went about it. What were helpful resources in their quest to learn more about this?

Third, how do you tell if the information is reliable or not?

There’s a ton of junk out there. Statistically, it’s probably more junk than not. How do you figure out which is reliable information and which isn’t?

I’m not sure yet. But I've found it helpful to go to the most expert possible source and figure out what they know. That will give you a baseline to start to assess what’s bullshit and what isn’t. Applied knowledge is information, and most of the community surrounding a topic usually repeat what the top 10% says and creates, regardless if it’s outdates or recently tested or not. You need to find that 10%, and figure out what they know.

For example, most VC’s repeat what the leading VC’s do. Leading VC’s, like a16z, sequoia, or YC, go down to the physics and investigate arguments themselves. They then publish the results, which are often consumed by lower-VC’s, who are often too lazy or inexperienced to conduct their own thought process, and will take these results as facts.
This works less in academia, where by default claims are questions. In industry, the 10% usually creates the literature and sets the standards.

Fourth, textbooks.

Textbooks are a great way to figure out the current consensus and literature on what’s going on within the community. They’r designed as reference points in which learners use to find information.
Blogs of leading authors/institutions.