This essay isn't a step-by-step guide to building 'Google', rather, a call for young people to consider entrepreneurship as a fulfilling alternative to traditional careers.
To maximise their chances of success, Paul suggests:
1. Become a builder: Gain expertise in technology or other fields you're passionate about. (Does not have to just be coding, either!)
2. Start personal projects: Build things you and your friends find useful. Paul suggests this is the fastest way to learn and potentially discover startup ideas.
3. Collaborate: Work on projects with like-minded people. This fosters skill development and could lead to finding potential cofounders.
I liked how Paul also emphasises the importance of good grades in order to access top universities, where you'll find other bright collaborators.
There are obviously many other paths, but if I wish I had this advice at 14 or 15.
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.
It might have been better if Paul Graham used one of the companies founded by YCombinator instead, but that would be less impressive to 14 to 15 year olds since those 4000 or so startups are not quite Google-scale yet.
To maximise their chances of success, Paul suggests:
1. Become a builder: Gain expertise in technology or other fields you're passionate about. (Does not have to just be coding, either!)
2. Start personal projects: Build things you and your friends find useful. Paul suggests this is the fastest way to learn and potentially discover startup ideas.
3. Collaborate: Work on projects with like-minded people. This fosters skill development and could lead to finding potential cofounders.
I liked how Paul also emphasises the importance of good grades in order to access top universities, where you'll find other bright collaborators.
There are obviously many other paths, but if I wish I had this advice at 14 or 15.