Ask HN: How do you store the knowledge gained in a day?
23 dennisy 48 5/13/2025, 6:23:29 PM
Each day I (and I assume most knowledge workers, devs, creatives) read many articles, papers, code snippets, AI responses, discord messages etc.
At the end of the day some of this information is most likely lodged in your brain and the digital version can be discarded. However some of it should be retained manually in some system - or at least I feel it should.
What approaches do people use to consolidate and store this information to allow all tabs etc to be closed for the next work day?
A lot are notes or links collections in obsidian. Others may be canvas on slack channels or conversations, some cloud note taking apps depending on with who I am sharing or collaborating on them, bookmarks in browser or RSS reader, even chats with ChatGTP.
In general it depends on where I got that piece of information or knowledge, what I plan to do with it, who I want to share it with and so on. There is no central consolidation process for all the diverse kinds of information, as there are "right" places to have them depending on it.
I have specific updates notes for each project. I add a weekly header (via a template) in reverse chronological order. Pull the key updates into that (I also have a todo for each project that pulls in tasks from all files in that project subfolder - so picks up meeting actions)
I also put them all in a canvas so when I doing updates about projects they’re all in one place.
I do the same for people I manage so I can keep track of updates and todos when I’m meeting with them.
My go to start point is a daily not where I throw in new tasks (tagged to projects or people) and those get pulled into the corresponding project/person file.
Because it’s markdown with lots of plugins it helps me do things like diagrams (mermaid diagrams) etc and excalidraw/canvas for architecting/mind map style ideation.
Search by file tags:
Search by contents:One thing to remember: most stuff can be forgotten safely. There are very few things you’ll actually want to look up a few months from now on…
Ctrl-F.
KIS
Ctrl-Effing-F
Any other trendy nonsense is time-wasting trifling foolishness.
To categorize the information, I simply link the entry to a specific page. For example, if I discover an interesting React library, I create a new entry like this: https://i.imgur.com/dDlStkZ.png
A great feature is that Logseq understands page hierarchies, so if I click on [[Dev/JS]], it presents a clear hierarchical overview: https://i.imgur.com/z9hGmmh.png
Using this approach, I've stopped bookmarking sites in my browser altogether. In Logseq, I can connect useful things to each other, add entire notes, and more, as shown here: https://i.imgur.com/Krld2cS.png
If I want to remember something, I just add a #card tag to the block, and it automatically syncs with Anki via a plugin.
I have a personal knowledge base that currently includes almost 7,000 files in which I store my notes. I take notes on everything. Every technology. Every project. Every meeting. Every product I evaluate. EVERYTHING.
My notes are stored in Org files that I edit with Emacs and Org mode[1]. Org files are written using a feature-rich lightweight markup language[2] that is much more powerful than Markdown (which is used by other note-taking tools like Obsidian). For example, Org supports plain text spreadsheets[3], a feature I love.
People tend to disqualify Org and say, "I don't use Emacs," while assuming that Emacs users choose Org because we already use Emacs. But I started using Emacs specifically for Org, not programming.
Regardless of which tool you end up using, consider organizing your note files using hierarchical tagging. I started using hierarchical tagging for my notes right after Wikipedia launched and I saw how effectively hierarchical tagging was being used there. Each Wikipedia article can belong to multiple categories, and each category can belong to multiple categories. This is hierarchical tagging, and it's worked great for my notes. At the bottom of every one of my Org files, there is a list named "Parent topics", and each parent file has its own "Parent topics" list (excluding the "main topics" files, which have no parents).
[1] https://orgmode.org/
[2] https://orgmode.org/features.html
[3] https://orgmode.org/manual/The-Spreadsheet.html
I question this premise. If the content you read on any given day did not the result in some change to your work product, it is really important enough to save it? Do you really need to remember all the messages, chats, articles that didn't give you any actionable answers? Or do you just keep the results that you created based on such things?
I keep none of it. I do, however, keep all my old code. Every throwaway line I've ever written is saved somewhere, even if it is just in git history on old throwaway projects. So when I do need to do something again, I don't need to re-do research or figure it out from scratch... I have my working solutions already stored.
I also decided that if something's worth remembering, I'll remember it. If it's not worth remembering, then I'm also not gonna both re-reading notes about it, no matter what note-taking tool or method I use...
My original method was a directory full of plain text files arranged by subject, that I brought up with my text editor.
Over the years I wrote a specification for a system tailored for my needs, that could manage different forms of media, notes, saved web pages, ebooks, and so forth. The spec grew until I set the project aside as more trouble than it was worth. In retrospect I wish I had kept going.
At the moment I'm using plain old hand-written subset of HTML linked to subdirectories arranged by subject. As time permits I will finish the (simplistic) custom browser, which will also let me annotate pages and edit files.
I have looked into some of the indexing programs that look inside files and index their contents in a searchable fashion. They all take a vast amount of storage space, probably because over the decades I have amassed a vast amount of data. After experimentation I decided to pass on the indexers as well. I have always managed things in a rigid hierachical arrangement, and it's pretty easy to find what I'm looking for. On the other hand, I know what's there and where I put it, which makes it easy for me. It would be much less useful for someone else.
Never underestimate the usefulness of a plain text file. It can be written, read, searched, and indexed by almost anything, should you wish to do so. Some of mine date back to the mid-1980s and MS-DOS 2.1, to OS/2 and Windows (briefly), Linux, and even Haiku. Every platform has subdirectories and some kind of editor; that's real portability. And if you ever have to deal with ancient machines that don't speak ASCII, much less UTF, there's probably some kind of conversion utility to let you move your files to IBM EBCDIC or DEC Sixbit.
If you're running emacs, the "org mode" add-in uses lightly-formatted text files organize data, which is then available within the editor. It's worth looking at if you're an emacs user, assuming you're not using org mode already.
Every thing else is Confluence in team spaces. And Jira. Slack too.
Things can be harder to find in Slack so that is more a second resort after Confluence.
Obsidian is a not-very-organized mess unfortunately; I still haven't figured this out but it's good enough for me to usually find things I remember. Confluence is organized as such https://docs.divio.com/documentation-system/. This works great.I always know where to put something and where to find it again later.
I also don't keep tabs open, I write things on a Todo list in Obsidian. Then at the beginning and end of the day I organize it; finishing small things like "record this", prioritizing, and moving project specific tasks to a page just for that project.
No file structure is ever gonna beat a good searchbar, adjust your own notes accordingly. I completely hid the file explorer. If I need to cluster things together, I use very specific key words at the top of the file (think: #Parent/Child), they're far more flexible than a file system.
Mostly organised in logical-to-me directory structure.
Local storage beats online-only in many ways, imho. Online content rots away over time. Whereas backing up local files is easy.
Beside that: browser bookmarks, simple note-taking app, and (last but not least) pen & paper.
I tried Obsidian for a while but I’m too prone to bike shedding with it, so I gave up. I DM myself in Slack with bits of info to keep around for the near term, because it’s already a simple feed ordered by time.
This is cool for links, but often I also want some nuggets/ideas to be saved.
You’ll almost certainly never look at 99.9% of it again so just move on.
Here's an idea: We should be able to record the full experience stream (or just the laptop screen, let's say) for a person -- digitize it suitably (eg. pull out all the text, or tokenize it with a VLM, etc), attach some metadata, and have the whole database ready for a person to query / play with, using powerful LLMs.
To the extent that you can store everything and perform effective recall/search, it obviates the need to carefully "pre-process" bits by noting them down in the right file, tagging them appropriately, adding metadata, etc. All of which should make for a much nicer UX.
Given the Jevons' paradox though -- I wouldn't be surprised if our experience stream becomes so dense/rich that storing everything and querying from it eventually becomes prohibitively expensive. We would then have to construct pre-processing rules to prune the stream, and amortize the cost of certain deductions by performing them at data ingestion time instead of repeating it for each query. It's all just the basic principles of system design at the end of the day, and how systems need to be rearranged as various component capabilities (and user needs) scale.
What you suggest is a nice UC for sure, but not sure it will make any of us smarter in the long run.
With your larger question, though, if there's specific information that I feel the need to keep locally, I add that to a wiki that I run. If information is in a non-online form (books, etc.), all I need to do is remember that it's in there. I don't need to remember the information itself because I can look it up at will. For everything else, I don't worry about it at all. If I found it online once, I can find it online again should I need it again.
But do you not believe there is some value in trying to store some of what you found / learnt each day, to allow you to make some new connections in the brain the following days?
Sure, but I retain some of that without having to do anything special. I have no need to remember everything. My brain seems to know better than I do what is worth remembering and what isn't anyway. I trust it.
Retention is even more likely to happen if it's information that I actually used that day, and if it's really valuable information, then I probably have used it immediately.
I will say, it's really helpful to open up excalidraw through Obsidian and create a quick flow chart or drawing with my team.
I suppose the exception is when I already have a project-specific doc set up, then links or thoughts related to that project will go in there. But even then, sometimes I use the default scratchpad first, and move the info later, the next time I'm doing dedicated work on that project.
I've personally given up and if I remember, that's great, if I don't, oh well. There is always more to learn tomorrow.
I don't worry too much about the structure. So long as it's written down and backed up, it is searchable, and that's enough.
The first folder - TODO is more like “Working memory” - unsorted interesting learnings, my actual todo list, notes and thoughts for the next few days
Then different sections for larger relevant parts of my life and memory
People Robots Company Code Reading ZanySchemes Family …etc
Whenever working memory is getting full I’ll take the time (30 seconds) to organise - either move or delete.
The key parts are - 1) Organise when it makes sense to, don’t try and design it all up front and don’t be scared of refactoring memories - the directory structure will anneal to something stable
2) have some damn discipline - tidy your notes, tidy your mind, and put the time and effort in, most people give up on note taking because they are too undisciplined to keep their virtual mind tidy, if you keep your notes tidy then up-keep is negligible, just like keeping your house tidy, maintain a high standard and then upkeep is easy
If a text file starts getting too big I’ll reorder it or split it out.
I think the key thing is developing the skill that suits you - don’t try and constrain it with some rule (all files must have structure X) because invariably something will not fit that pattern and then you’ll give up or spend too much effort trying to find the holy grail of data structures and then you’ll give up.
Let it flow naturally without constraints, it will settle on a form that is useful
I advised them to avoid it because it would be shameful for them to be used like a marionettes, but I guess if they stopped it would be even more shameful. There's something about their pride of being covert that makes it easy to use for this.
Sometimes it stores stuff that I don't care about, but that's fine.
I also do handwritten notes sometimes.
Initially I didn't want to do it, but it's so reliable and predictable, that it became useful for that. I can't explain the exact mechanism either.
I also have problems storing some things. Like I wanted to store information about Tourettes and coprolalia, but it doesn't stick to my herd of scammers (maybe some of them have it and they're embarrassed?). That's the best example I can give (a non working example, but that's fine, no storage medium is perfect).