My thought on reading this is that people should explicitly not constrain idea selection to software. I think this leads in bad directions. There are tons of people who want to make software. The way to improve the world is to get out there and build stuff that most software people don’t think is possible. (I was the tech founder for Wave, but Drew’s non-technical abilities were far more counterfactually important than my tech skills in terms of making huge progress on important problems!) Software skills are super-relevant in all industries.
There will be room for software in almost any project.
And you suggest that their current sense of what they’ll feel excited to do is.. not important? (Sorry, this sounds like I’m strawmanning what you’re saying, but I don’t understand it)
Would you correct my probably wrong understanding?
My thought on reading this is that people should explicitly not constrain idea selection to software. I think this leads in bad directions. There are tons of people who want to make software. The way to improve the world is to get out there and build stuff that most software people don’t think is possible. (I was the tech founder for Wave, but Drew’s non-technical abilities were far more counterfactually important than my tech skills in terms of making huge progress on important problems!) Software skills are super-relevant in all industries.
Repeating in my own words to see if I understood:
You’re suggesting that potential CTOs do an idea selection process
And find any useful idea, not just in software, and do that one
Even if it is “create a nuclear shelter for EAs” or “Work on Tobacco Taxation”
Because that’s how one does the most impact.
There will be room for software in almost any project.
And you suggest that their current sense of what they’ll feel excited to do is.. not important? (Sorry, this sounds like I’m strawmanning what you’re saying, but I don’t understand it)
Would you correct my probably wrong understanding?