Following Curiosity

The advice is always linear: finish one book before starting another. One project before the next. Focus. Complete. Move on.

I've tried it. It doesn't work for me, and I don't think it's a character flaw.

Curiosity doesn't queue. It doesn't wait for you to finish the thing you "should" be doing. It pulls. A passage in a novel echoes something you read in a history book last week. A bug in Project B reminds you of a pattern from Project A. These connections don't respect your reading list or your roadmap.

Let ideas collide

I keep two or three books open at once. Different subjects. Different tones. A technical manual, a memoir, something on design. It looks scattered. It isn't.

The best insights arrive in the gaps—when you're not actively trying to solve a problem. You're halfway through a chapter on typography and suddenly see why your component layout feels off. You're reading someone's memoir and a line about patience reframes the way you think about iteration.

Cross-pollination isn't something you schedule. It happens when you give your mind enough raw material from enough different inputs.

Parallel inputs, compound returns

The same applies beyond books. Podcasts, conversations, rabbit holes at 1am—every input is a thread. You don't know which ones will weave together until they do.

The trick is variety. If everything you consume is from the same domain, the ideas just confirm each other. But pull from different worlds—design, history, science, someone else's craft—and the overlaps become surprising. A concept from one field becomes a metaphor in another. A constraint you read about becomes a tool you reach for.

Trust the pull

Following curiosity means trusting that the thing pulling your attention might be exactly what you need—even when it looks like distraction.

I once spent a week deep in a book about game design when I was supposed to be finishing a web app. It felt indulgent. But the way that book talked about feedback loops and player motivation completely changed how I thought about user interaction. The "detour" became the most useful week of that entire project.

The book you "should" finish can wait. The thing tugging at your attention might be the missing piece for something else entirely.

Follow the pull. The ideas will find each other.