DEV Community

Cover image for I've bookmarked 300 articles "to read later" and never read a single one. So I built a system for that.
Yao Long
Yao Long

Posted on

I've bookmarked 300 articles "to read later" and never read a single one. So I built a system for that.

I have a bad habit.

I see a good article, bookmark it. I see a useful snippet of code, save it. I get a great take, I save that too. My bookmarks bar has more than three hundred links in it now. Nine out of ten of them have never been opened since the day I saved them.

Not because I didn't want to read them. Because once I saved them, I couldn't find them again.

Open the bookmarks bar and there they are, three hundred of them, all squished together, each one looking like it's from the last century. The article about query optimization you saved last week — you probably don't even remember its name, let alone dig it out of that pile. After a while I stopped saving things. Every bookmark felt like I was making room for something I'd never see again.

So I switched to a notes app. Saving was easier, but a new problem showed up: I'd taken the note, but when I needed it, I couldn't remember I'd had it. Notes lying there, one by one, like they'd been dropped into a bottomless box. You definitely saved it, but every time you need it, it's like you never did.

I tried to fix this.

I tried tagging every note. I tried sorting everything by topic. I tried giving folders really thoughtful names. Every attempt worked beautifully for the first two weeks. By week three, it started leaking. By week four, it fell apart, and I never touched it again. There are three half-dead "organization systems" in my drawer right now, and they all died from the same cause: I couldn't be bothered to file things.

That's the thing. I just didn't want to file. Energy is limited. I've already spent a day writing code, and now I have to figure out "which category does this note belong in" just to save it? Three days of that and I'm done. One bad day and the whole thing's abandoned.

Eventually I realized the problem wasn't that I was lazy. It was that I made "saving" too complicated. Saving should be effortless — throw it in, done. And when I want it back, it should know where it belongs.

So I built a system.

Last summer I spent three months building myself a knowledge base in Notion. It does one very plain thing: what you save, you can find again.

It's made for people who write code. I called it Dev Knowledge Hub. A few specifics:

You write a note and give it a topic. That note automatically joins the list of everything else under that topic. Next time you want to review that topic, all of it — notes, articles, code snippets, whatever you were thinking at the time — is waiting on one page. No more digging.

You save a code snippet and link the article you got it from. Now, when you go to use that snippet, you'll know where it came from and why you saved it. No more staring at a line of code wondering why.

You're preparing for interviews. Interview questions link to your study notes, so when you review a question, the related knowledge you saved sits right there next to it.

Plainly: it glues your fragments together so they remember each other.

I've been using it for almost a hundred days. I haven't abandoned it. I couldn't stick with a workout app for two weeks before this.

Don't pay. Try the free version first.

I turned this system into a template and put it out there. There's a free version and a full version. But I'd tell you to start with the free one.

Not because the free one is enough. Because I don't want you to buy off my description. I've bought too many things that "sounded great."

The free version is called Lite. The core stuff is all there, I just cut the heaviest features. Spend a few days throwing your usual scattered stuff in there, and you'll feel the difference. It's not the same as "saving things."

Dev Knowledge Hub — free template

If you use it for a week or two and think "that's it?", then don't buy the full version. Keep the $29. We're even.

If you use it and think "hmm, something's missing" — then the full version is probably what you want. The full version has a whole set of advanced features, and there's an intro page inside the free version. I'm not going to recite the feature list in this post. Look for yourself.

$29, one-time payment. Free updates. 14-day money-back if it's not for you.

And here's a less conventional offer.

I want to trade the full version for your honest review. First 20 people, each gets a one-time code. The full version, free.

One condition: after you've used it, tell me whether this thing actually works. Whether it truly solved your problem, or I'm just fooling myself. Negative reviews are welcome. I almost want them more — "I hate this thing" is worth ten times more than "it's great." When all the codes are gone, I'll update this post.

Comment "I'm in" below, and I'll send you a code.

At the end.

If your bookmarks are sitting there with dozens of saved links, none of them ever reopened — we are the same person. This thing was made for you. Take it, use it, and tell me the truth.

Top comments (0)