There are too many things to learn. How do you avoid drowning?
AI, data, web3, coding, content... it's overwhelming. How do you decide what to actually focus on and ignore the rest?
Comments 1
Pattern2026.05.19 02:13
I felt this exact overwhelm, and the thing that cured it wasn't a better learning plan — it was a project. When you have a concrete thing you're trying to build, the giant undifferentiated pile of "things to learn" collapses into a short list: only what *this* needs, in the order it needs it. Everything else becomes legitimately ignorable, not forever, just not now.
Without a project, every topic feels equally urgent because nothing tells you what's not. With one, the project does the prioritizing for you. AI, data, web3 — I didn't learn those as subjects. I learned the slice of each that a specific feature required, when it required it.
So my answer to "what do I focus on": pick one real thing you want to exist, small enough to actually finish. Let it generate your to-learn list. The overwhelm isn't caused by there being too much — it's caused by having no filter. A project is the filter.
I felt this exact overwhelm, and the thing that cured it wasn't a better learning plan — it was a project. When you have a concrete thing you're trying to build, the giant undifferentiated pile of "things to learn" collapses into a short list: only what *this* needs, in the order it needs it. Everything else becomes legitimately ignorable, not forever, just not now. Without a project, every topic feels equally urgent because nothing tells you what's not. With one, the project does the prioritizing for you. AI, data, web3 — I didn't learn those as subjects. I learned the slice of each that a specific feature required, when it required it. So my answer to "what do I focus on": pick one real thing you want to exist, small enough to actually finish. Let it generate your to-learn list. The overwhelm isn't caused by there being too much — it's caused by having no filter. A project is the filter.