11–20 of 38 posts
I put new facts into Anki ( https://apps.ankiweb.net/ ) and then they get reviewed daily, with a steady, slow addition of new facts. It's a very effective way to keep everything in long-term memory. (It's also very difficult. You're trying to recall items that are just at the edge of your memory.)
Usually you get a fair amount of review just from the stuff you read while searching for other stuff you know is in there somewhere.
Keeping a daily journal with relevant work and discoveries is great. You can use a simple text editor and keep appending the current date to the top of the file and writing a few a lines. You can do one per-project, or a general one for your daily life and activities. I reel back through the tape every few months when I'm curious about the timeline of development/research/discovery. Whittling it down, I think of it a…
What do you mean by learnings? Actual skills or facts like TIL?
I keep a log of things like "here's the parameters for tar to extract a file" (yeah, I know, there's man pages, but not all systems have them). I review that item when I have to extract files from a tar archive. Until then, I don't care if I forget it - that's what the file is for.
Started documenting the things I learn in a section of my website called "snippets". It's purpose is to be a registry of copy-paste resources, like a personal stack overflow, and I'm trying to keep it as small and short as possible. Also I don't write things there right away. First they go in a "backlog" in my notes, and once I require the knowledge but forget the details I transition it into a post on the website. T…
Keeping a daily journal with relevant work and discoveries is great. You can use a simple text editor and keep appending the current date to the top of the file and writing a few a lines. You can do one per-project, or a general one for your daily life and activities. I reel back through the tape every few months when I'm curious about the timeline of development/research/discovery. Whittling it down, I think of it a…
Does the logs stick to your memory when you go through a bunch of them together at once every few months ? Will it not be an overload at one go ?
I find it terribly distracting to have all the things that I have tried to learn in my "active" memory. So I cycle between phases where I am engaged with a subject for a while, and then move on to the next item in my (circular) list until I cycle back to the original subject again. This is a serious impediment to developing any useful expertise in any area, but I have sort of made peace with this tendency. But not al…
(copy-pasted with modifications from my comment on a similar thread posted earlier) I used to have an elaborate system, but I converged on a simple solution: I stash everything in a single Google Docs document. I made the conscious decision to optimize for ease of use, so that the friction/effort to write something down is minimized. At the same time, I also made a decision to not to adopt any organization system --…
The doc should have grown over time. Do you just append to the doc as you learn something new or do you organise learnings within the doc. I am asking this because if there is no structure there wouldn't there be too much of context switches when you go over them ?
Earlier quoted context omitted.
Does the logs stick to your memory when you go through a bunch of them together at once every few months ? Will it not be an overload at one go ?
What do you mean by "learning?" because I mean something specific: the ability to adapt to solving new problems. It's not something that is so easily reified and commodified. If "learning" is remembering a password or a combination of keystrokes, I would argue that that is closer to "rote memorization" and does not really reflect the character or qualities of "learning" that this method is more suitable for. You shou…