We live in an era of unprecedented learning abundance. Online courses, tutorials, documentation, videos: the bottleneck on learning has shifted from access to attention. There is simply more to learn than any human can process, and the problem of choosing what to learn has become as hard as the learning itself. I've spoken to a lot of people in tech who feel paralyzed by this. They know they should be learning something. They just can't decide what. In the indecision, they consume content — tutorials half-watched, courses half-finished — without the satisfaction of actually building anything.
The myth of staying current
There's a specific anxiety that tech culture produces, which I think of as the "falling behind" feeling. It says: if you're not learning X right now, you're already behind. It's constantly updated as X changes. This year it's AI, next year it will be something else. The feeling is real. The conclusion it suggests — that you need to learn everything currently labeled important — is not. Most things labeled important now will be far less important in three years. Some things labeled boring now will turn out to matter a great deal. The ability to tell the difference is itself a skill, and it's one that takes time to develop.
"The question isn't 'what should I learn?' It's 'what kind of thinker do I want to become?' The answer to the second question makes the first one easier."
Choosing deliberately
Building skills intentionally starts with a question most learning advice skips: what are you actually trying to do? Not in general, but specifically. If you're trying to become a better engineering leader, the most valuable thing you could learn might be how to give feedback, not the latest framework. If you're trying to build something new, the most valuable skill might be tolerance for uncertainty, not more technical knowledge.
Technical skills compound better when they're in service of something you care about, rather than acquired in response to ambient anxiety about falling behind.