Hacker News new | ask | show | jobs
by VoodooJuJu 1073 days ago
I used to be deep into the personal knowledge management tar pit. Most of it was wasted time. Here are the few things in it that I actually regularly use and get something out of. These are just simple zim-wiki text files that I update and skim through a couple times a month:

- Idea list: Ideas for art or other projects that I'd like to try some day. I'm occasionally adding new ones and I've started work on old ones I've added that finally piqued my interest.

- Gift idea list: Things friends and family may hint at wanting or outright say they want in casual conversation. I add stuff to this list then buy it for birthdays, Christmas, etc. Can get some real nice surprises for people when they only mention things in passing and you happen to catch it.

- Book list: Just a wish list of books. Occasionally I'll buy a few to add to my personal library and cross them off the list.

Just understand that most of the personal knowledge management stuff is a waste of time. It's a bunch of feel-good busywork that's typically sold to you first as a cheap idea, then sold to you as products like Roam Research, Obsidian, etc. Can't really beat simple lists in text files or on paper. I even like physical notebooks that you go through and keep a hand-written index in the back of. Forces you to think and revisit stuff.

2 comments

I use the nearly the same.

- Zim-Wiki for items or procedures that I refer to or repeat often. Zim-Wiki is mostly plain text and transportable, but handles embedding small screenshots. I keep another Zim-Wiki notebook for small projects or investigations. - A simple text file list for in progress items or projects that I am working that have more or less an end date or specific goal - A simple text file list for to-do items, vague plans, and links to check. This file changes almost daily. - A simple text file list for wish list items and purchase ideas > syncthing on all my devices to keep all them all current

In my paid work I have a few additional things, but not much more. The most important is a separate subdirectory for each project's files. Structure it so that it is ready to use in a retrospective repository when finished. Refer back to it often when planning similar projects.

I used to "hoard" knowledge, had a large library, sets of sorted bookmarks files, etc., but I'm finding that I need less and less of that. I think the biggest change took place when I made a short project once with the goal of making my home computing portable and self-hosting. That really simplified a lot.

A big help is being consistent in a format and structure that makes sense to you regardless of the tools you migrate through.

Yeah I have to agree. I really liked the idea of having some sort of common place book of files on my machine, but I never looked at them. I have a few todo/list files like you mentioned and aside from that, I dump old ticket and historical data from my day to day into dated files in case I need them. I rarely do, but it's easy to dump since they're fairly raw.