My ~Flow~ of Knowledge

My flow (version 0.1) is based on The Knowledge Cycle:

1. Research #

Source
- It’s okay to be an omnivore as long as you keep your plate and tablecloth clean.
- What
  - Articles: RSS reader (NetNewsWire, shifting to self-hosting), mail inboxes for newsletters, social media
  - Books and Essays: Apple Books, PDF reader
Screen out those that I’m going to read
- Use my mobile devices.
- Do this to kill time when queuing, waiting…
- How
  - Send to a separate email address for later reading and archive.
  - Delete those that I will not read. Don’t pile it up again.
Save/Archive
- How
  - Pocket and Readwise Reader currently, shifting to save as *.md files Raw *.md files go to my OneDrive and later my NAS. Only keep notes and quotes in Obsidian.

2. Reading #

If the content can be understood by reading it once, don’t read it twice. If it should be read twice, then make a bookmark.
If I want to highlight, leave relevant notes as well.
Read articles on the computer, and books on the iPad.

3. Taking lasting notes #

Note cards and reference cards (quotes): Obsidian
Highlight will be moved from Readwise Reader to Obsidian reference cards

4. Compose blog posts based on notes #

Scheduled/Structured writing projects: Logseq as my to-do list and to categorise
Topics derive from readings: Start the cycle again
Curation: Hybrid project to share great articles, highlights, notes

To get into this pure flow, step 0 is to: clear up my email inboxes, RSS reader, browser bookmarks, Books app on my iPad, and Telegram channels.

If it’s possible to subscribe via RSS, then embrace the good old RSS.
Curate the newsletter subscription list. Only keep those you feel necessary to be notified when new pieces come.
- Receive important push notifications only. (especially for Telegram channels)
Minimise the usage of social media.
Don’t follow the same public media on different platforms.

Why I leave platforms #

The main reason I turn to raw *.md files and Obsidian is my upgraded appetite for long-lasting information as someone diagnosed with the collector’s fallacy and currently under treatment. I want to keep what I’ve read offline and store it locally, so no worrying about platforms shutting down, page URLs going invalid, or authors deleting the whole site (I know it’s their right to do so, and it’s also my right to download the public internet). This reduces my monthly expenses on SaaS, too.

~Flow~ #

Inspired by the Zettelkasten blog series, I created this page to document my daily routine (or let’s say, flow) of processing information and turning that into solid knowledge. I try to craft an organised, for-the-future, and go-offline-at-any-time learning system, so this page works as a storyteller of this journey, a guide for anyone who looks for similar purposes, and my manifesto to stick to this routine, flow with the flow.

While looking for suitable tools, I thought of starting a webring to gather insights into how others manage their knowledge and arrange their working/learning process, including tools and theories they employ. This can serve as a community to discuss, or an index for internet nomads to discover new ways and perspectives.

But why limit it to only be about productivity, about knowledge management? I simply ask myself. Every pursuit and every lifestyle has a unique flow in it to tell the story of who I am, and taking a peek into how others live, not just the “boring” how-you-take-notes, can give us so many fresh ideas and stories, same as what now pages, Hacker Station, and The Proof has been doing. So this is ~Flow~, a webring working as a bookmark to collect people’s flows, and a line connecting dots with thoughts on the internet. It can be about how you manage your knowledge, brew coffee, write codes, spend an ordinary Sunday afternoon, research, create, and many more. It is about you and your way of life.

More importantly, sharing your flow with others via a single webpage might help you establish a way that you can stick to, keep changelogs, and iterate for a very long time. I’ve been caught up in productivity tools for some time, doing nothing but digging the App Store, SSPAI, Product Hunt, and v2ex to find new apps. And this makes me almost forget the real support behind—thoughts. Tools are here to reduce the coefficient of friction in your workflow, but this coefficient starts at such a low level and will not bring a strong impact on your dependent variable, which is your solid output. This passion towards tools/applications seems to be alike coffee lovers pursuing better coffee machines, pots, percolators, or filters, but there’s no tangible result like a cup of wonderful espresso for you to enjoy without good coffee beans, water, and temperature. Coffee machine to coffee is what productivity tool to productivity.

Jot down your flow, practice it, make it better, and write down why—it’s a fresh start.