templatePath: _default/baseof.html

templatePath: partials/nav.html

For the Wynn

I write to think. Here are my thoughts.

Kind: page

Type: posts

Section: posts

BundleType:

File: things-left-unimplemented-dot-dot-dot-and-i-m-unsure-if-i-ever-will

GitInfo: { 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC}

IsNode: false

Layout:

Ancestors: Pages(2)

templatePath: _default/single.html

Things Left Unimplemented… and I'm Unsure if I Ever Will

Published:

Personal Knowledge Management

This post is part of the Building My BASB in Emacs - 2023 Capstone Report series.

Having been around the PKM block a few times, I’ve gone snipe hunting once or twice in the PKM space. Here are some pitfalls I’ve found.

Importing Readwise Into BASB

In the past, I’ve included importing Readwise comments in my implementations of BASB.

It was often a pain to set up, created a lot of name conflicts when searching (which might be valuable to some, but wasn’t to me), had occasional problems with unsupported characters, and generally just didn’t give me anything useful. With Logseq, I actually was running a separate instance of Obsidian because the Readwise plugin there worked and LogSeq’s didn’t. What a mess.

It did help when I was tinkering with a more formal Zettelkasten implementation, but beyond that… not so much.

Speaking of Zettelkasten…

Implementing Zettelkasten

I’ve alluded to this a few times, but I’ll be more explicit here.

I’m very intrigued by the Zettelkasten community and approach. It feels like there are some good ideas in there.

However, it also seems very clearly tailored for jobs where creating new, original knowledge is your goal and the thing that makes you successful… aka. Academia. For almost every other job in existence, remixing knowledge that already exists, or coming up with better implementations of current approaches, or just driving toward clarity instead of entropy are FAR better ways to spend your time and energy.

There is very real overhead in trying to make a Zettelkasten work. And to use it well, it gets more difficult to traverse through as it grows, by design. After all, if you’re trying to knock a bunch of these notes together to spur new ideas, that’s an exponentially growing number of collisions you’re aiming for. In creating novel knowledge, you want that. In a world with deadlines, that’s friction that just isn’t needed.

So, even though org-roam talks a big game about Zettelkasten, I find it much more useful as a general ID linker tool than that.

The one possible personal exception I might tinker with someday is a personal philosophical/religious Zettelkasten. That’s a pretty unique domain where thoughts from your own mind disproportionately matter, and connecting them together might yield meaning in and of itself. We’ll see if I ever get around to that.

templatePath: partials/series.html

Building My BASB in Emacs - 2023 Capstone Report series

  1. My Path to Org Mode
  2. Should You Choose Org Mode?
  3. What Makes Org Mode Hard for PKM
  4. My BASB Implementation in Org Mode v2023-06
  5. Things Left Unimplemented… and I'm Unsure if I Ever Will

templatePath: partials/footer.html