Should I aim to build a unicorn, or just quietly write code and earn some money?

This question is actually a classic "crossroads" that many tech professionals encounter. Behind it are two fundamentally different life pursuits and ways of living. Neither is inherently better; the key is to see which one suits you more.

We can imagine these two paths as two different roles:

The first type: Be a "Captain," aiming to discover new continents (unicorns).

• What you'll do: Your core task is no longer rowing (coding), but studying charts, setting courses, finding investors, recruiting crew, distributing provisions, and boosting morale. You might not touch an oar for years, spending every day dealing with people issues, financial issues, and directional issues. Code is merely a tool you use to build the ship, while your goal is the "voyage" itself – leading the entire fleet to a place no one has ever been.
• What you'll endure: 99% of ships sink halfway; this is the norm. You will face immense pressure. The livelihoods of your crew, the expectations of investors, and the lack of understanding from your family will all weigh heavily on you. You might not have a stable income for a long time, and there will be no boundaries between your life and work.
• Your reward: If successful, you gain an entire new continent. This is not just immense wealth, but also the sense of accomplishment from changing the world and defining the rules. Your name will be written in maritime history.

The second type: Be a "Master Craftsman," aiming to build the best ship (quietly coding for a living).

• What you'll do: Your core task is to build the ship to perfection. You'll research the best timber (architecture), design the most scientific sails (algorithms), and use the most exquisite craftsmanship to connect each component (writing elegant code). You can single-mindedly delve into technology, becoming an irreplaceable expert in your field.
• What you'll endure: You might not be able to decide where the ship goes; most of the time, you'll be executing the captain's orders. Your sense of accomplishment primarily comes from the work itself, not the final destination. The ceiling is relatively clear, and it's hard to achieve exponential returns like a captain.
• Your reward: You will have a very decent and generous income, a stable life, and extremely low risk. You have a clear career path and can live a good life anywhere with your skills. You have your own time to enjoy life's pleasures beyond technology. Your value lies in your professional depth and irreplaceability.

So, you can ask yourself a few questions:

1. What do you enjoy more? The sense of accomplishment from "managing people, securing funding, and acquiring resources," or the thrill of "solving a complex technical problem"?
2. What do you dislike more? Endless meetings and communication, or a bug that drives you crazy for days?
3. What is your attitude towards risk? Are you the type who believes in "succeed or die trying" and enjoys the high-stakes gamble, or do you prefer a secure life and a good night's sleep?
4. Ten years from now, how do you want others to introduce you? "This is the founder of that listed company," or "This is the most brilliant tech guru in our company"?

Finally, I want to say that these two paths are not one-way streets. Many people first work as "craftsmen" for several years, accumulating experience, capital, and connections, before deciding to become "captains." There are also many "captains" who, after a failed voyage, return to being "craftsmen," and precisely because they gained a global perspective, they become even more master craftsmen.

The most crucial thing is to be honest with yourself. Figure out what you truly want deep down: do you want to "own the world," or do you want to "understand the world"?