I don't disagree with Paul's choice to focus on entrepreneurship and getting rich here. If you're looking to excite people, tell an exciting story. Captivate imagination. No one gets pumped up (especially at that age) at the mediocre story.
What I find great about his advice is that it is by no means limited to entrepreneurship. Working on passion projects, doing well in school, and learning how to build relationships is valuable even if you're working for someone else.
There's a big space in tech jobs between the "grinding away at code/help desk" and "startup bro" that I feel doesn't get described enough. And that's one thing I'd tack on to Paul's advice, notwithstanding the need to sell the message above. That advice he espouses can also lead to being a really standout contributor at a tech firm, and probably with a higher rate of success than getting a startup to stick. One doesn't have to form a startup to contribute ideas, and there's good money to be made in that space.
I think your choice of wording above is important to call out: The advice "maximizes" the chance of success; but it doesn't guarantee it.
> "I think your choice of wording above is important to call out: The advice "maximizes" the chance of success; but it doesn't guarantee it."
This is a great observation!
I agree that Paul is framing an inspiring narrative, especially when targeting younger people. You're spot on, suggesting that this advice sets people up for success in general, whether they become entrepreneurs, standout employees, or something else entirely.
We need more narratives about those successful 'in-between' tech roles.
Paul's giving the ingredients for good outcomes, but the recipe is up to the individual.
I don't disagree with Paul's choice to focus on entrepreneurship and getting rich here. If you're looking to excite people, tell an exciting story. Captivate imagination. No one gets pumped up (especially at that age) at the mediocre story.
What I find great about his advice is that it is by no means limited to entrepreneurship. Working on passion projects, doing well in school, and learning how to build relationships is valuable even if you're working for someone else.
There's a big space in tech jobs between the "grinding away at code/help desk" and "startup bro" that I feel doesn't get described enough. And that's one thing I'd tack on to Paul's advice, notwithstanding the need to sell the message above. That advice he espouses can also lead to being a really standout contributor at a tech firm, and probably with a higher rate of success than getting a startup to stick. One doesn't have to form a startup to contribute ideas, and there's good money to be made in that space.
I think your choice of wording above is important to call out: The advice "maximizes" the chance of success; but it doesn't guarantee it.
Overall, completely agreed. =)