Using a blog like a zettelkasten seems like a good idea

· Around 6 minutes

Having recently gotten back into the swing of reading via RSS, I spotted a post from Mike Crittenden called Blogging as a Zettelkasten.

It touches on the idea that a blog can act as a zettelkasten. For the unfamiliar, a zettelkasten is nothing more than a big collection of notes. While you might imagine reams of snippets dumped into a tool like Apple Notes, the difference is that each note (or “zettel”) is generously interlinked with other notes so as to form a “web of knowledge” or a “second brain”. Each note should address one standalone idea such as “English is an unproductive language” rather than a more generic “Notes on languages”.1

The very blog post I just linked is a good example of what a zettelkasten note would look like. There are a number of hyperlinks scattered about and rather than reiterate previous ideas, you can just link to prior knowledge that has been expanded in detail elsewhere, should the reader choose to follow.2 As time goes on, themes start to appear, not unlike one of those crazy pinboards you see detectives use.

It is said that new insights should just sort of “fall out” by putting ideas in close proximity where your brain can make all the connections it likes. Your brain already works this way for the most part, like when you have a eureka moment in the shower, and so the idea is to basically make that process as easy as possible. While most examples seem to have degenerated into YouTube productivity clickbait, “How to Use Roam to Outline a New Article in Under 20 Minutes” is still a golden example of what this process looks like. That was probably the single most thing that made me raise an eyebrow in interest.

Now then, while I’ve already generated enough content for a “What I don’t like about zettelkasten software” type post later on, this post is best kept succinct and in line with the title so let’s touch briefly on why I think using a blog as a zettelkasten seems like a good idea.

1) Longevity

The main issue that should concern anyone semi-serious about zettel software is that you’re inherently dealing with information that may be retained for quite some time, if not possibly an entire lifetime. In the grand scheme of things, software itself is not a very old medium and yet, it feels like some ecosystems tend to degrade within mere months, if not years.3

The beauty of just using a blog, and particularly a static site backed by any text-based format, is that it… I was going to say that it “degrades gracefully through time” only to realise that humans are incapable of original thought and there is no such thing as free will.

I also can’t help but notice that a lot of the attempts in this space are from relatively fresh startups, rather than long-term established companies. Not that either is necessarily more equipped but the idea that Roam Research has raised $200 million in funding, as opposed to bootstrapping, is absolutely horrifying to me.

On the face of it, I’m sure users are happy that Roam has the cash to make the app nice and crisp but the idea that you would entrust any amount of long term knowledge storage to a business that will inevitably be ripped apart by venture capitalists in 5 years when it doesn’t turn on a profit on “Joe Schmo’s 40,000 hyperlink sprawl regarding himalayan pinecones” isn’t exactly comforting.4

2) One System To Rule Them All

Trying to have just one way of doing things is often not ideal because you’re probably forcing unrelated things into one box.

In this case though, I find having multiple systems for writing is annoying. Blog posts are just text and “zettels” are just text so why not have one workflow for dealing with both. It may be that different software is required (whether web-based or desktop software) or even a unique plain text format such as org-mode in the case of org-roam

Less software is always nice, right?

3) Reliability

There’s one piece of “zettel” software in particular that comes to mind where I fumbled some magical formatting code in the web editor and destroyed a post beyond recognition. While it was backed by Git, everything autosaves so I had to do some unwiring. I actually chalk it up to user error but if I can’t trust myself to not break the software (as has happened twice), then perhaps the UX unavoidably has to be called into question.

I also remember Roam Research used to suffer from some site troubles back in the early days. It isn’t hugely comforting knowing that your knowledge might be inaccessible whether it be on a train or in a car.

4) It’s hidden in plain sight (a secret rant)

Part of me has come to associate “zettelkasten” with the whole “Productivity Porn” movement. The idea is nice but the wider fanbase often gives me pause. To be clear though, I think a lot of that ecosystem floats around YouTube and Reddit rather than say, the home of Jethro Kuan’s elisp child.

Also, who the hell is Tiago Forte? He’s like a bargain bin Elon Musk who just appeared out of thin air one day and no one seems to know why. Why are people paying this man $5000 to go right click ➡ “New text file”? I don’t understand.

Anyway, in that vein, blogging feels like a zettelkasten hidden in plain sight. It carries all of the benefits of one without having to think about the wider ecosystem and that sounds pretty comforting.

Having convinced myself that reducing the scope of each blog post is probably a good idea while writing this post, I’ve now got an entire scrawl of at least 5 different topics on my normally empty whiteboard.

I haven’t even done anything yet and so far, it seems pretty promising!

Footnotes

  1. Can I just take a second to say that it feels massively ironic that most of the literature around zettelkasten topics are so dense to the point of giving me a brain aneurysm.

    Like, just go back and have a look at that earlier link for zettelkasten. What the hell is that?! That’s a thesis, not an introduction!

    It’s almost as bad as that New York Times recipe that starts off by referencing 9/11.

  2. Wait a minute, the internet is basically just one big zettelkasten?!

  3. I’ve recently been stuck in a dilemma with Gatsby between “Oooh, looks shiny” and “This is going to erode in like 2 years, isn’t it”.

    It does actually have some nice functionality but whether it’s worth the risk is an important question, not to mention the insanity that is node_modules.

  4. While that might seem like an overly negative view, and congratulations to any business that survives the pitch meeting/incubator gauntlet, I can’t help but believe it never ends well as you get deeper and deeper into funding, and the later investors also want their 40,000% return.

    Slowly, the crushing expectations of higher profits cause you to reduce the feature set and raise the price or maybe you’ll manage to IPO and jump ship with a nice bag of cash before the whole thing starts slowly sinking into the ocean.

    The foundations feel unstable right from the second you sign the agreement.”