bliff

I do create a new text file each time, although it's sort of arbitrary what I group. Sometimes I will put my entire day's notes for a given book in one file. Other times I'll have atomic notes for each thought.

The organization process is wholly dependent on how much I come up with in a day/week. I mostly read for fun now, so I don't have to rigorously organize lecture notes or anything like that for later use. On the other hand I'm pretty rigorous with how I process tasks. As a ballpark figure I'd say 30-60 minutes per week, or 5-10 minutes per night.

To your latter point, I think that's fair. The main idea is to be flexible and recognize when you need new categories or whatever (and when you can dump unhelpful ones).

My system lately has been to write every note as a raw text file that I save to a git repository on the fly. Later I process these notes and give them Zettlekasten style IDs. This step forces me to organize the knowledge: either everything gets a fresh ID (e.g. "25"), or it gets a derived ID that relates it to whatever subject or task it's related to (e.g. "44a3b9"). But it also means I can stream thoughts into a lightweight inbox without having to do the organizing upfront.

I then have derived categories from the main stream of thoughts. If the thought is a task, I further process these into categories. I have recurring tasks and events that I handle on a "Time" page that is effectively a calendar, and I have one-off tasks that go into a Kanban style backlog.

What I really got from Zettlekasten is that trying to establish your system upfront is a mistake. Things inevitably leak through your categories and then you lose faith in your system. By just having a running stream of thoughts and then relating them after the fact and deriving categories afterward, you get the benefits of organization without a lot of its failure modes.