What are the best ways of absorbing, and maintaining, knowledge?
Recently, I've collapsed (ascended?) down/up a meta-learning death spiral -- doing a lot less of reading actual informative content, than figuring out how to manage and acquire such content (as well as completely ignoring the antidote). In other words, I've been taking notes on taking notes. And now, I'm looking for your notes on notes for notes.
What kind of scientific knowledge, techniques, and resources do we have right now in the way of information management? How would one efficiently extract useful information possible out of a single pass of the source? The second pass?
The answers may depend on the media, and the media might not be readily apparent. Example: Edward Boyden, Assistant Professor at the MIT Media Lab, recommends recording in a notebook every conversation you ever have with other people. And how do you prepare yourself for the serendipity of a walk downtown? I know I'm more likely to regret not having a notebook on hand than spending the time to bring one along.
I'll conglomerate what I remember seeing on the N-Back Mailing List and in general: I sincerely apologize for my lack of citation.
Notes
- I'm on the fence about Shorthand as a note-taking technique, given the learning overhead, but I'm sure that the same has been said for touch-typing. It would involve a second stage of processing if you can't read as well as you write, but given the way I have taken notes (... "non-linearly"...), that stage would have to come about anyway. The act of translation may serve as a way of laying connective groundwork down.
- Livescribe Pens are nifty for those who write slowly, but they need to be combined with a written technique to be of any use (otherwise you're just recording the talk, and would have to live through it twice without any obvious annotation and tagging).
- Cornell Notes or taking notes in a hierarchy may have been the method you were taught in high school; it was in mine. The issue I have had with this format is that I found it hard to generate a structure while listening to the teacher at the same time.
- Mind-Mapping.
- Color-coding annotations of text has been remarked to be useful on Science Daily.
- Speed Reading Techniques or removing sub-vocalization would seem to have benefits.
- Once upon a time someone recommended me the book, "How to Read a Book". Nothing ground-breaking -- outline the author's intent, the structure of his argument, and its content. Then criticize. In short, book reverse-engineering.
- Spaced Repetition. I'm currently flipping through the thoughts of Peter Wozniak, who seems to have made it his dire mission to make every kind of media possible Spaced Repetition'able. I'm wondering if anyone has any thoughts on incremental reading or video; also, how to possibly translate the benefits of SRS to dead-tree media, which seems a bit cumbersome.
(I've also heard a handful of individuals claim that SRS has helped them "internalize" certain behaviors, or maybe patterns of thought, like Non-Violent Comunication or Bayes Theorem... any takers on this?)
- Wikis, which seem like a good format for creating social accountability, and filing notes that aren't note-carded. But what kind of information should that be?
- Emotionally charged stimuli, especially stressful, tends to be remembered to greater accuracy.
- Category Brainstorming.Take your bits of knowledge, and organize them into as many different groups as you can think of, mixing and matching if need be. Sources for such provocations could include Edward De Bono's "Lateral Thinking" and Seth Godin's "Free Prize Inside", or George Polya's "How to Solve It". I'm a bit ambivalent of deliberately memorizing such provocations -- does it get in the way of seeing originally? -- but once again, it could lay down the connective framework needed for good recall.
- Mnemonics to encode related information seems useful.
Loading…
Subscribe to RSS Feed
= f037147d6e6c911a85753b9abdedda8d)
Comments (40)
You may be very interested in a document I came across a while ago, which is one man's manifesto on note-taking that he compiled in a (free) ebook called "How to Make a Complete Map of Every Thought You Think." You can find it here: http://www.speakeasy.org/~lion/nb/
The program he sets forth is extreme, as he is quite literally trying to detail and commit to memory (on paper) his entire mind. But it contains a lot of useful advice on how to take notes that are useful, accessible, and memorable. I've implemented bits of his system and it has helped a lot in school - I've found that it's much easier and more useful to take notes when there is some method to the madness.
Oh, and if you are at all a visual thinker, Always take notes on paper. Paper offers freedom that lines of computer text simply can not: arrows, diagrams, color of pen, relative sizing of text corresponding to its importance, arrangement of elements on the page, all of these things are immediate, intuitive, and completely your own. I'll cite a paper that highlights the importance of this sort of visual language: http://www.stanford.edu/~rhorn/a/recent/artclNSFVisualLangv.pdf
I saw this! I wanted to bring it up in another LW thread on how detailed a map should one make of one's own map. The author wrote, albeit anecdotally, that he lost a creative edge while in the process increasing his mental clarity.
I didn't post the topic because reading the stream-of-consciousness may have proven a chore to some. But thanks for bringing it up.
I've also thought about this a lot.
My conclusions, in summary, are that the best way to know more stuff over the long term is reading ebooks and the internet and putting everything useful into an SRS.
Cornell notes, shorthand, mind-mapping, livescribe: who cares? You don't need to take notes. Any method of learning that involves writing down what someone says they read (it's called "university") is ridiculous. Almost anything that can be taught by a person can be taught better by a book.
Speed-reading: perhaps, I haven't done much research. Honestly, gathering new info is a tiny subset of the whole "learning stuff" problem. It's the easy part. The hard part is keeping it in memory, for which: SRS.
Mnemonics: this may be worth learning. However, most things which are worth learning can either be learned without mnemonics or only require extremely basic mnemonics (namely, linking / association). The stuff where mnemonics really shines, like memorizing long strings of numbers of decks of playing cards, is pretty much useless in real life. The stuff that's useful is textured data, data that's coherent and meaningful enough to not need mnemonic techniques (apart from simple linking/association), for instance math or programming or physics. You don't need mnemonics to learn the pumping lemma, but you do need an SRS.
One thing I've been experimenting with recently is to use SRS creatively. I add my own ideas as cards to an SRS system, and just read them every time they're due for review (failing them if the idea seems unfamiliar). Another thing I'm trying is to use SRS to re-expose me to things I've read. If you see a nice LW article, just up and copy the whole thing onto an SRS card, then just look over it when it's due for review. You can add notes to each card about how much time you should spend, like whether you should just skim over the article or read it in detail. If you're reading an ebook, just copy each section into your SRS as a re-exposure card (in addition to adding all useful facts in as active-recall cards).
Seriously, SRS with ebooks just completely subsumes all other techniques for learning stuff.
This comment gave me an interesting idea that I shall try next semester, so thank you!
In every lecture/class/seminar one attends, put exactly 3 things from that lecture into an SRS deck, and then that should cover almost all the revision required.
(The write-3-things-down idea comes from another person... possibly a famous mathematician, does anyone know who?)
For making notes I wrote an open-source hierarchical plain-text editor Notilo. It is basically a Notepad with tree structure. There were a few similar programs, but none of them had all of the features I wanted (free, Unicode, saving in database, no special syntax). The program is not finished yet; it works correctly, but it should be more pleasant to use and better optimized for very large documents. (I have stopped the development when the proverbial 20% of features fulfilled 80% of my needs.)
In real life I keep a bunch of A7 papers (for US readers: a letter size cut to 8 pieces) in a plastic envelope and a small pen. The papers are small enough to put in my pocket and bring almost everywhere. Later I write the notes to computer and discard the used papers.
Recently I made a habit to write down almost everything I learn about programming (that's my job), because I have noticed a knowledge loss when I work with some technology, then a few months or years I work with other technology, and then I come back again. This didn't happen to me when I was younger, because when I moved to a new technology, I did not return to the old one, but these days I am using a few different technologies in parallel.
(Once I thought that having a "personal wikipedia" could be great, but I don't want to put private information on internet and running a web server on a personal computer makes it very slow. But there are some programs that provide similar function without the web server.)
Today the computer media are cheap and it is easy to record anything. Problem is, your day has only 24 hours and the Moore's law ain't gonna help you about it. It could be interesting to record every conversation you ever had, but when will you listen to them? And what is the point if you won't? You need to system to search your database; at least provide some keywords to each conversation, so you can search the keywords.
Recently I've been using Evernote to organize my notes. It has a nice phone app that I can use to take quick notes while away from my computer, a computer program, and a browser plugin that lets me clip articles. When it comes to notes I try to think that every time I record an idea I would have forgotten, it is roughly equivalent to thinking of one new idea.
I tend to write out outlines after I finish books or some interesting articles partially to see the arguments more clearly and to refer back to in the future.
It's always interesting/fun to go back browse old ideas I've forgotten about.
I'm currently working on a piece of speed-reading software. It works as a browser plugin, creating a floating window in which words flash a few at a time, so that you don't have to move your eyes, and to keep pace.
If people have ideas about features it should have, I'd be interested. For example, how valuable would it be to pause after each paragraph (or group of short paragraphs) and show some sort of summary? For example, it might extract all the proper nouns and low-frequency words and make a tag cloud.
Why do you think any of that will improve reading speed? What are your goals for this software? E.g., do you want to help slow readers (150wpm), or are you trying to help fast readers (350wpm) become considerably faster?
My reason for thinking the flashing-words-in-a-window thing will increase reading speed is that there's already software that does it, which has been confirmed to work. Most people don't use them more than briefly, though, because of the inconvenience.
My own experience was that brief usage of a speed-reading tool increased my reading speed while not using that tool, and that using a speed-reading tool increases my reading speed by enough to justify filtering most of the things I read through one.
Software that does it (google-friendly phrase: "rapid serial visual presentation") has been available on all the major platforms (Windows, Mac, Linux) for at least 15 years. I know from personal experience that on Windows and Linux, the software worked reliably and without any annoying glitches or performance problems. Yet hardly anyone uses it more than briefly. What exactly is this confirmation that you speak of that would move the expected value back to anywhere near where it was before taking into account that hardly anyone in the last 15 years has used it more than briefly?
"Hardly anyone": am I wrong about that? Can you name two people who do not have a large financial or academic-prestige stake in it who have ever used it more than briefly?
It is not enough to show that it has benefits. You also have to show that it does not have major drawbacks that cancel out the benefits. I have a specific drawback in mind that with probability .88 cancels out any benefits for the vast majority of potential users. It is not ignorance on the part of computer users or inconvenience. My experience with using it on Windows 95 and Linux was that although it would be more convenient if softwares like browsers and operating systems were better integrated with it, the inconvenience of using it is not particularly high especially after one takes into account that the user can reserve its use for longish passages while handling short passages the ordinary way. (Do not recall the name of the Windows RSVP software I tried. The Linux software was call sview.)
What drawback did you have in mind? I'm confused why you would allude to this without specifying what it was, and curious as to whether it's one I've already thought of and tried to mitigate, one that I've thought of but can't mitigate, or one that I haven't thought of.
I will explain the drawback I have in mind if you answer my two questions in grandparent to my satisfaction.
My reason for holding back on the explanation of the drawback is that it will require an appeal to one or two highly technical concepts (from the field of neuropsychology roughly speaking), and I know you well enough by now to know that you will probably latch onto the highly technical concepts and refuse to write or think about the only part of this thread of conversation that has any significant interest to me: namely, the fact that, unless I am extremely mistaken about your plan, you already have enough information to know that your plan of creating yet another RSVP software is a waste of time even if I had made no mention of any drawback. I predict that you will persist in not updating on this information you already have.
You seem to be under the impression that I'm implementing naive RSVP with a slightly improved UI. I've made improvements that I haven't told you about, and I'm experimenting with different variations on the concept. I believe that people don't persist with RSVP because the software is bad - in addition to the inconvenience of getting started, they periodically force task loads into timeslices where they don't fit, which derails the reader badly. I wrote my own software because I believe I've found ways to reduce how often that happens, and to reduce the disruption when it does.
If you think you know something about RSVP that I don't, just say it. Don't play games.
Are you going to follow up on this?
I would rather just drop it because grandparent's score is currently at minus 3, and by convention downvotes mean, "I don't want to see more like this".
The downvotes are for the "I will only explain if you answer my questions first" thing. If you have insights about RSVP, I do want to hear them.
(Upvoted back up to 0 because this is an entirely reasonable response! Why on earth would someone be expected to want to continue a conversation in which they were getting downvoted?)
You may not have read the context of that comment. Here's how the conversation went, from my perspective:
rhollerith: Hey, I know something very important about the project you're working on right now.
Me: And what's that?
rhollerith: Not telling. You'd just ignore me anyways. (-2)
Me: Don't play games.
...
Me: Are you going to follow up on this?
rhollerith: I'd like to drop this conversation now because I was downvoted.
Needless to say, I am quite unhappy with how this conversation went. But ending it there would make it much worse, since I don't know whether rhollerith actually noticed something important, or is defecting by accident, or if I offended him somehow and forgot about it.
RSVP (Rapid serial visual presentation) software has been around for a long time. What makes yours better? Color bars changing as you get closer to the end of a sentence/paragraph, and an extra delay at the end of a sentence/paragraph seem to be the most useful extensions.
I can vouch for being able to read much faster, at the cost of comprehension using RSVP tech.
The main problem I've had with speed reading software has been structure, and with regularly using them. I would like for there to be a pause or something at the end of each paragraph, and beyond that ease-of-use is the most important thing.
The link goes to Prof. Boyden's university profile, which doesn't mention his note-taking habits. This is all I could find after spending five minutes on Google:
Does anyone here know where more information about Boyden's approach is to be found?
http://www.technologyreview.com/view/409043/how-to-think/
Thanks!
I find that annotating articles really helps me retain information. This was hard for me to do online until I found diigo.com. there are some other sites that are listed on wikipedia, but this one is the best IMO.
You don't generate the structure and make annotations and summary during the lecture or reading, you do those afterwards during your review of your notes.
One key in studying is to not to try to do too much at the same time. Read, then go back and underline or take notes, don't try to underline during the first read-through. Review and condense/summarize then, not while taking the notes. During later reviews, just read the keyword and try to explain it from memory. Active, not passive - the more focused you are on what you are doing, the better you will retain it.
I note that you leave out recall.
You might want to do some research into "mnemotechnics". Also: Baddeley's model of working memory is quite interesting.
Alan Baddeley's popular book Your Memory: A User's Guide is a very useful resource. Because it shows the best understanding of how memory actually works as well as tips and tricks it lets you build further on those techniques. (I haven't seen the 2004 edition linked to. I read the first edition from 1983 and don't know what changes, if any, were made.)
Deliberate, as SRS incorporates active recall per definition, methinks.
For any materials learned through SRS, sure.