Tinker

I think there are roughly two ways people relate to work. For most people, work is a means. It funds the rest of life. For a smaller group, work is also an end - a form of expression, a way of making sense of the world, a place where curiosity gets to act on reality.

Neither category is morally superior. The world needs maintainers as much as it needs obsessives. But if you are in the second group, a lot of conventional advice will quietly deform you. You will be told to optimize for stability, work-life balance, legibility, optionality. None of that advice is insane. It is just aimed at a different kind of person.

The people who want work to be an expression of curiosity usually make one mistake early. They think the path will be revealed by enough advice. Read enough frameworks, study enough successful people, collect enough heuristics, and eventually the right direction will become obvious.

It won’t.

Not because the advice is false, but because it is backward-looking. Steve Jobs had the line about connecting the dots only in retrospect. That is true of almost all career and innovation advice. Someone succeeds, then looks backward and builds a narrative about why. But the narrative was not the map they followed. It was the story they told after they arrived.

Innovation has no script. Bell Labs did not produce Unix, C, and the transistor because someone found the perfect framework on the internet. Xerox PARC did not build the GUI, Ethernet, and laser printing by executing a tidy roadmap. People were tinkering. Building, testing, breaking, rebuilding. Following a line of curiosity even when it looked inefficient from the outside.

That is why I prefer tinkering to studying. Studying matters, but only if it feeds contact with reality. The point of fundamentals - physics, math, biology, computer science - is not that you will use every theorem directly. It is that fundamentals expand the space of things you can notice, connect, and build. You cannot connect dots you do not have.

Then you tinker. You build things. Most of them are bad. Some fail immediately. A few surprise you. Over time, you start noticing patterns in what holds your attention, what kinds of problems feel alive to you, what you are unusually good at seeing. That is how you discover what Naval calls specific knowledge. Not by introspecting forever, and not by consuming other people’s certainty, but by building enough that your own pattern becomes visible.

Specific knowledge is discovered, not taught. A classroom can give you raw material. A book can give you concepts. A mentor can save you years. But none of them can tell you what your own frontier is. They cannot tell you which questions will keep pulling you back, or which kinds of work turn effort into attention instead of depletion.

What changed is that this path used to require institutional access much earlier. If you wanted to do serious computing, biology, or engineering decades ago, you often needed a university lab, a corporate research group, or expensive equipment you could not get on your own. Today the tools are dramatically more accessible. You can train meaningful models on a laptop, publish to the world from your bedroom, prototype hardware with cheap components, sequence DNA with tools that would have sounded absurdly cheap not long ago. The excuse of total exclusion is weaker than it used to be.

That makes a lot of self-improvement culture feel like motivational theater. It gives you the feeling of movement without the risk of contact with reality. Reading about lifting is not lifting. Reading about startups is not building. Reading about innovation is not innovating. Frameworks can clarify experience, but they cannot replace it.

So the real path, if there is one, is brutally simple. Learn fundamentals. Build things. Fail. Build again. Notice what keeps calling you back. Follow that signal harder than is reasonable. The explanation comes later.

Authority cannot tell you your path because there is no path before you walk it. If you are wired to tinker, the barrier is usually not resources anymore. It is the belief that you need permission, a roadmap, or enough certainty before you begin.

You don’t. You start building, and the path appears under your feet.