I, along with many others in AI safety, believe there is a shortage of generalists in the community and that there exist many projects and efforts that by default will not happen unless they are owned by a strong generalist[1][2][3]. As someone who is a reasonably good generalist, I decided to assemble a reading list of the essays and blog posts that have personally helped me the most. I would love others to comment with pieces they think should be on this list.
The crux of this reading list is the idea that if you're working hard as a generalist on a project you care a lot about, then by rigorously applying the lessons from these documents you will improve more quickly than you otherwise would.
By the numbers:
I've attached 18 documents to start this reading list.
The authors cited more than once are Paul Graham (5), Ben Kuhn (4), Ethan Perez (2), and Greg Brockman (2). Sam Altman and Eliezer Yudkowsky also have their fingerprints over a lot of the content.
The items are 15 blog posts, 1 blog comment, 1 interview transcript in blog post form, and 1 book.
If I were to recommend one single item from this list it would be this one because 1) it's good to understand the ways in which otherwise-intelligent people are unstrategic, and 2) it's good to understand the ways in which you are not automatically strategic. I have gotten a ton of mileage in my short career thus far simply by being more strategic. The defining trait of the most effective coworker I've ever had is that he is unrelentingly strategic.
The original post is great but domain-specific. Ngo's response shows the more general principle that winning whack-a-mole doesn't conclusively discredit forward-chainy approaches.
Project leadership
How do you get projects done when your boots are on the ground?
Some of the advice is domain-specific to AI safety research, but the document as a whole provides great guidance on becoming an excellent IC, in particular an excellent managed IC, across any domain. Some good bits are the ones about making your work legible to others and scoping your project timelines appropriately.
Interpersonal/organizational
How can you understand the structure of an organization and contribute positively?
The Elephant in the Brain ended up being the best book for organizational psychology by virtue of being the best book for human psychology in general. I think that the first section which goes over the broader theory of signaling is the important part to read. Understanding the values and motives of the people around you can help greatly in navigating complicated settings, but of equal importance is understanding that the core lens also applies to you: you're a silly monkey trying to signal its genetic fitness via unstated means in order to increase status and sexual marketplace value like the rest of us.