Ask HN: How to take notes and learn from them?
The zenith is the center of the night sky and it is used for orienting.. so on and so forth
Maybe even throw in a couple of links to other notes for good mesure.As I assemble more and more info, what differentiates my vault from a local-copy of wikipedia? I mean sure it's not a word for word copy ( I always try to use my own words as much as possible) but is it any better?
And if being similar to wikipedia isn't a problem, then what constitutes as learning? having a copy of wikipedia on-hand definitely is not learning. so do I take a look at these notes every couple of days and call it a day, or take a test on the subject as if it was a college course?
This happens for me with other subjects too, for example a couple of weeks ago I wanted to get really knowledgable about greek mythology so I picked up mythos by Stephan Fry (great book btw) and again I was unsure about how to take notes on it.
my intuition said to briefly explain in the form of short bullet points the plot point of each sub story in the book as well as detailing the relationships between different gods mentioned in the book. I guess that's better that not taking notes at all, but is my written relationship guide really better then the 10s of graphical ones available online?
I used to know how to take notes for school because I got used to the structure of exams in different subjects thanks to the decade+ being a student but when it comes to free-form learning where there isn't a test or any tangible way to mesure progress I lose sight of how to take notes/learn
For me, Zettelkasten seems like way too much work, and the goals of it are not my goals. So while I do use Obsidian, I don’t use Zettelkasten, I never use the graph view, and I have very few links. For it to really pay off seems like you need to turn your notes into your digital garden. What’s really wild is the guy who came up with the system did it by hand with index cards, if I remember correctly.
Obsidian isn’t too opinionated, and there are a lot of plugins, so you can make it into whatever works for you. Zettelkasten disciples have some impressive looking graph views, but I do question how much of that is actually valuable vs procrastination.
The tool aside, I wouldn’t worry about there being something online that already exists or is better. The act of doing it yourself helps with the learning process. Any time I made a cheat sheet in college for a test they allowed it, I never needed it. The act of making it got me to learn it. I saw an interview with someone recently who said they still write book reports as an adult, like they did in grade school, because it helps them learn the lessons of the book and organize their thoughts around it. All of this takes a decent amount of discipline when there is no external force holding you accountable. If it’s worth it or not really depends on the person and topic.
Talk with yourself on it, relate that with other things you know, search or question some IA about the doubts you have, even do the effort of categorize correctly the information in Obsidian is doing some work around it.
And that on pure intellectual information, if you can put it in practice, do something based on that, test your own understanding, not what is literally written there, helps even more.
I read source material (dev docs, Wikipedia, whatever) and reformulate the concepts in my own words, adding my own analogies and elaborating where needed.
A lot of what you said sounds like you don't necessarily get value out of keeping notes for all these random topics.
Until you have a well-defined purpose for taking notes, consider not?
Taking notes from lectures depends on the course. You can't go back to the lecture, plus you might believe it's a guide to what is on the text. It depends on how much is the whim of the teacher. In a lit class, take notes. If it is introductory chem you can probably get it all from the book and the problem sets. [1]
When you're doing original research though, it is all about the notes. I filled up about 30 notebooks in the process of getting my PhD, you really should document every little thing that you try.
People do it less but you should do the same if you are doing any kind of engineering. Not least if you want to file a patent you want your whole invention process documented so you can prove you invented it.
Even in programming you should keep a notebook of your thought process and debugging. Personally I find I write better quality code when I work with an LLM because it forces me to take better notes.
[1] I wound up taking intro chem when I was a senior and a better student and got the top score in the class even though I rarely attended it. It did get a tiny bit of help: the prof told us we could skip one quiz, I did, then went to the chem lab to ask the T.A. to skip the test, he said "Why not take it right here?" and he looked at it and handed it back to me and said "Are you sure about that?" I thought it through again and realized my mistake.
- note-taking by hand (including analog mind-mapping);
- rewriting/reorganizing your notes once or twice, again by hand;
- writing a succinct, ELI12 explanation of the subject, again by hand (a/k/a the Feynman method), then later trying to do it again from memory, and comparing the version from memory to the original to see what you forgot to include.
Sometimes making and reviewing voice recordings of you explaining everything aloud can work similarly, but there is something special about handwriting.
Once you've actually learned everything, you can put it into a spaced recall system like Anki to actively recall/review periodically to prevent forgetting, but at that point it should be pretty well internalized.
I find Obsidian and its ilk good to store, link, and share a "final product" of something you have already learned. That final product can also be original work based on something you already know and have internalized — but at that point you're an expert.
In my experience, trying to use Obsidian to do the learning and the memorization/internalization is barking up the wrong tree.