Ask HN: Maintaining a searchable work diary/agenda

Why not go back to a Filofax?<p>I mean search only has to be good enough and maybe a Filofax is good enough or you can make it good enough through progressive change to the way you use it.<p>This is premised on the fact that you have experience with the tool and have had many years to better learn what works for you since you have used it.<p>To put it another way, a Filofax might be the simplest thing that might work for you because you can pick up where you left off.<p>And if nothing else, using a Filofax again will give you a clearer idea of what you don&#x27;t want (learning from failure)...it might be the case that you like the idea of being a person who maintains a diary&#x2F;agenda more than the fruits&#x2F;labor of maintaining one (not maintaining a dairy&#x2F;agenda currently would be consistent with that).<p>Anyway, software wise, you could do worse than OneNote (and quite likely better) with the caveat that I am the type of person who likes the idea of being the type of person who is organized on paper more than I like the fruits&#x2F;labor of being organized on paper.<p>Good luck.

I just have orgmode files. One for day job, one for hobby projects, and one personal. Fun fact: I have been playing with querying it with a local LLM, and it’s quite usable, although I can also find information via fuzzy search&#x2F;grep too.

Zim wiki or just text files in a folder. Nothing special. Don&#x27;t get special with it. Waste of time.<p>I use zim-wiki for simple searchable lists. I also journal, but hand-write everything. Keep a few pages blank in the back for an index. Then when I fill a journal, I go back and read it, and write out an index on those last few pages. Keeps things as searchable as is possible for a dead-tree diary, at least the important bits and keywords.<p>Creating an index like this forces you to revisit, evaluate things. Forces you to think through what&#x27;s important, what to take away from what you&#x27;ve written. You may take away very little (and that&#x27;s okay).

I guess what do you need? I use Obsidian with the daily notes plugin. They sit with my other notes. I have a day planner on paper just because I&#x27;ve found paper to be useful for disposable things like tracking what I spent my time doing in minutia, but electronic notes good for things I&#x27;ll want to reference later like questions, to-dos, deliverables I was working on, road blocks I ran into, etc. I might transfer my paper notes into my electronic one sometimes if it happens to be relevant.

Big plug for logseq here. After trying Evernote, Apple Notes, Roam Research, Obsidian, and Logseq, I&#x27;m finally happy.<p>Obsidian has got strangely popular... but for me Logseq wins because of the block-based way of working (which Roam also has) is much more flexible. Instead of just making monolithic notes, you can measure data points, reproduce blocks, query data, etc. You are crafting from much more flexible clay.<p>I can interlink all around my knowledge base. I can, in my daily journey, add points under tags or headings, that I can then query in reverse. I can make pages from blocks on other pages. I can keep track of meeting types, specific meetings, individuals at them, topics, etc. It is flexible enough to be very powerful but also doesn&#x27;t need me to make upfront decisions. I can just build things out day by day.

I&#x27;ve been using GitHub Projects lately<p>1 classic project for my check lists. The cards are open and I use check boxes to check them off as I perform them.<p>1 non-classic project for my tasks. I create a title only card and added a &#x27;status 2&#x27; type (25%, 50%, 75%, complete, waiting, staged) and another field for the type of work (Paperwork, maintenance, project a, project b)<p>I&#x27;m also using Microsoft Sticky Notes to track pending work.<p>(I haven&#x27;t found anything I like yet)

I use obsidian &#x2F; vscode as an editor for markdown files, but keep the files as basically pure text.