> All he's really saying is 'you need to be executing on your ideas to be happy, not just thinking about them.' Which is true for a lot of people, myself included.
Oh, sure, I don't doubt that's true for many people, it's true for me as well. However, in order to easily test various things, you need to have a lot of people/datapoints to work with.
It's amazing if you have a product that many people want to use and resources with which to bring your ideas to life, but most people who own companies are probably too busy getting those companies to profitability (or improving it) to try any big ideas.
It seems to me that the author had the liberty and ability to try new things a lot (look at the experiments he lists), which requires a good team, an audience to test your idea with, etc...
However, in order to easily test various things, you need to have a lot of people/datapoints to work with.
I don't know, I've built lots of things that look amazing in my head, but appear far less amazing once I've actually implemented it. While I am just a single data point, the process can provide enough information to realize that it was a bad idea.
I will agree that having more data points has its place, but building it just for yourself is often worth it.
Oh, sure, I don't doubt that's true for many people, it's true for me as well. However, in order to easily test various things, you need to have a lot of people/datapoints to work with.
It's amazing if you have a product that many people want to use and resources with which to bring your ideas to life, but most people who own companies are probably too busy getting those companies to profitability (or improving it) to try any big ideas.
It seems to me that the author had the liberty and ability to try new things a lot (look at the experiments he lists), which requires a good team, an audience to test your idea with, etc...