To Remember Everything You Learn, Surrender to This Algorithm (2008)
wired.com
wired.com
https://www.youtube.com/watch?v=c-4xOe79epU&list=PL3MozITKTz...
https://www.youtube.com/watch?v=QzBoDe3PgAc&list=PL3MozITKTz...
Glutanimate has taken Anki to a whole new level. He created a painless UI for occluding any part of an image and making Anki flashcards out of it (Image Occlusion Enhanced). I used it to efficiently create and memorize thousands of anatomy flashcards. Ordered lists can be a real pain to memorize, but when not missing steps is crucial (as it is for medical OSCEs), Cloze Overlapper has worked very well.
Anki lets you share your decks with others, and medical students have collaboratively created very high quality study decks for studying for the various STEP exams.
To be honest, I was always a fairly mediocre student. Big-picture concepts and figuring things out on the fly, no prob. But I've always struggled to nail down bits of information long-term or learn sequential information, meaning calc and ochem required inordinate amounts of time. No longer the case. Spaced repetition plus visual/text/auditory learning is a recipe for success.
The possibilities here should not be underestimated. Folks on Hacker News have talked about the value of information commons, and this right here is the next best example behind Wikipedia I have ever encountered. While quality collaborative decks exist for things like medical school, learning languages, and more, none exist specifically for the program I am in (PA school). I am currently creating my own with the goal of it being the core of a quality collaborative deck. I am using Gephi to spatially organize concept maps for diagnoses complete with incidence and strength of associations, when such information is available. I then export these maps to Anki, use Visual Occlusion Enhanced to block out the information I want to recall, and voila: time-efficient first-time learning and long-term retention.
Tips and best practices:
* Effective learning: Twenty rules of formulating knowledge[0]
* A list of Anki tips and suggestions that [a medical student] wrote[1]
* Anki Guide for Medical Students[2]
* How to make high quality Anki cards quickly[3]
* Anki Tips: What I Learned Making 10,000 Flashcards[4]
[0]: https://www.supermemo.com/en/articles/20rules
[1]: https://www.reddit.com/r/medicalschool/comments/4ocdyb/a_lis...
[2]: https://drwillbe.blogspot.com/2011/08/anki-guide-for-medical...
[3]: https://managingmedicine.org/2013/05/14/how-to-make-high-qua...
My question: I have hundreds text files that are solely highlights I want to remember. I’ve made my own cards (for other things) for years and know that’s a best practice, but for this I want to automate the process more. Anyone have a suggestion to format long texts into many cards as quickly as possible? Script, Keyboard macro, or just general method?
However, the transfer can be wildly better than trying to swallow a big pile of Facts (TM) solely by using them. Despite being superficially more work, Anki-memorizing+using can get you to mastery on topics with much less net time spent than simply straight-up using, as long as it is a task that involves a lot of "brute facts" of some sort.
This misconception wrecked my first couple of attempts to get into it, because I did not get the results I thought I should get. Better understanding has yielded better results.
I want to use Anki so badly. I have bought the app on iOS ($25), but I haven't been able to get it to stick. I think the hardest part is to distill things into brute facts.
It seems like most the facts are trivial and obvious if you know the concepts and I haven't been able to map my concepts to something on an Anki card that would be useful for spaced repetition. IMO concepts are not something that you "forget" once you have done all the work of putting the pieces together in your head.
I would love to hear success stories of people using spaced repetition successfully for things that aren't facts.
I've only used spaced repetition for learning languages myself (vocabulary but also conjugations and declensions when applicable) and it's true that it generally works better when you can easily match something 1:1 to make both sides of the card. When you can't easily reduce something to a very simple and understandable expression it can get quite abstract and difficult to use.
For instance if you're making a deck to learn French you could make a card that says "une chaise -> a chair", no problem here. But now if you want to translate the word "encore" you have a problem because it can mean a bunch of different things in English: still, yet, even, again... Here making a card can create more confusion than nothing in my experience. It might be better to include it in short sentences demonstrating one specific meaning at a time, like "il est encore en retard" -> "he's late again".
Same thing for grammar: "je pense" -> "I think". Easy. "tu pensais" -> "you (sing. inf.) thought (imperfect)". Not so easy. For these things spaced repetition can only get you so far, you really need to practice the language "in context" to make it stick.
An interesting thought would be to have some interactive anki cards.
I don't know about the details, but it could be something like, don't show me a card "how to list files using bash", show a command prompt, and if the user types a command that list files (tree, ls, find, etc.) approve the answer. Maybe ask "list files as many ways you can remember), etc.
How would this translate to other kinds of knowledge? Probably not easy, but not every card would have to be interactive, just the ones that make sense.
As a very long time Anki user who only very recently started using plugins, I agree with this.
I mean, I think vanilla Anki is already awesome and gives you tons, and I've used it that way for years. But yeah, there are some amazing plugins which can take things to whole other levels, especially in very visual fields.
Glutanimate makes great videos that introduce the plugins (and he writes/maintains some of them, including imo the above two).
But the basic idea is: Image occlusion - allows you to make a "cloze" using an image. I.e. you select 3 parts of an image to hide (by drawing something over them), and then you get 3 cards, one with each thing being hidden, then having to be revealed. That's the basic gist, and it's amazing, especially if you're studying something with lots of drawings (I usually don't, but e.g. anatomy is useful. And even I find uses for it).
Cloze overlapper allows you to easily create something that's recommended in the famous SuperMemo learning article. Let's say you want to memorize a song. You write the lines of the song, then the plugin generates cards which go:
Card 1: Song name [...] (you have to know the first line)
Card 2: Song name
The first line [...] (you have to know the second line)
And so on. So you're getting the context of the last line of the song, and then you have to know the next line.
This is the "standard" way to learn something like songs, poems, etc, but also useful for other ordered lists of things. Incredibly customizable btw (how many lines to show, whether to show line after as well, etc).
Other fun things: Image Resizer - simply a button that allows you to paste a smaller version of an image.
Advanced browser - makes the browser way more awesome (specifically, it gives you the option of sorting by arbitrary columns).
Note: Anki 2.1 just came out, and most plugins aren't compatible yet. So it's a real question whether it's worth upgrading if you rely on plugins.
The best spaced repetition method for me is listening to music. If I watch a film 5x or see a flashcard 5x or read a comic 5x, I'm bored. But I can listen to the same song 20x and still like it.
I'm about to take another stab at Spanish and vocabulary is one of my perennial weak points. I've played with Anki before, but it didn't seem as useful as I have been told.
Is it possible to get DroidAnki to have notices telling me that it's time to study something?
> I am currently creating my own with the goal of it being the core of a quality collaborative deck.
You can do that? How does one contribute to a public deck on Anki?
Eventually I dropped Anki for the (closed source and freemium) memrise and I've been using ever since, I currently have a one year streak going. When learning vocab it actually asks you to write it down, or pick the correct translation from multiple choices which makes it a little less repetitive and more stimulating. It also has a few professionally made decks for some languages which are pretty decent in my experience. In the end it works a lot better for me.
But again maybe it's anki's defaults that aren't for me, but if that's the case they're pretty mediocre defaults IMO.
E.g. if your note field is called SpanishWord then putting {{type:SpanishWord}} in your card template means you're prompted to type the answer. (And Anki will show you a diff between your answer and the content of the field, so you can see spelling mistakes immediately.)
The pics from the Anki android app on the Play store shows how it works: https://play.google.com/store/apps/details?id=com.ichi2.anki...
Specifically your last part sounds like an awesome approach to learn and remember. However, I see a lot of difficulty in sharing the resultant cards and getting comparable outcomes. You probably need to set up the connections first by creating the cards. Simply having access to the cards may lead to people not taking the time and effort to bootstrap the connections by learning about them in a comprehensive manner. Also some organization that works for you may not necessarily work for some other person.
Nevertheless, I am very much intrigued by the potential of sharing knowledge this way. I just think it's not a clear cut and easy problem as one might imagine at first.
(created an account just to write this)
Eventually, I did not have the time or need to keep reviewing the cards, so I stopped. But I intend to pick it up again after cleaning up the cards after my PhD. I highly recommend the software.
One piece of advice: I treat these flash cards as basically fast tests that trigger a review if you fail. I recommend this approach as many people seem to think flash cards can only be definitions. Some of my cards are definitions, some are short problems, some are proofs, etc. The definitions are unit tests. Problems and proofs are integration tests. Both are necessary.
I study maths and I never thought about using flashcards for it, but it's a cool idea, I might try it out!
Making your own cards is more effective than using someone else's deck, simply because it's tailored to you. For anything other than a language, unless it's pop trivia, you should try to make your own cards. You typically have to work methodically through the thing you're trying to learn, which can help a lot. If you go with a pre-made deck then you're relying on what someone else thinks you ought to know.
I tried a few of them and the quality varies. The Arabic one I tried was very funny, it would show you something, like أ, and then ask: does it mean "Alif" the letter o does it mean: "How much wood would a woodchuck chuck if a woodchuck would chuck wood? A woodchuck would chuck how much a woodchuck would chuck if a woodchuck would chuck wood".
Pretty useless.
That could be solved by not treating flashcards as units of knowledge you need to memorize, but as tests that you can only pass if you know a certain set of things. Then you would simply add new things to learn (e.g. vocabulary, grammar rules) and the system selects appropriate flashcards from a large set of examples to test your knowledge.
I've been working on something like that using example sentences from Tatoeba, but I didn't get very far yet, partially because defining the set of learnable grammar rules for a language I do not speak yet is a bit difficult.
Personally I used Langenscheidt's Basic German Vocabulary¹, which contains the most common 4000 German words, further divided into the top 2000 and the 2001st-4000th and by topic, with example sentences for all of them. I made a card for each of the top 2000 words and included the example sentences in the cards as well.
[1] https://www.amazon.com/Basic-German-Vocabulary-Langenscheidt... (I found a used copy sold online for about 10€, it can be a bit of a pain to get one)
This is usually a google search away.
Premade decks are really good for starting off, but ultimately making cards pays off more in the long run for associating memories to individual cards. This comes at a cost of a longer setup time and ongoing process, but with this you can guarantee all your cards are of high quality caliber.
I have my own CSS Stylesheets on my cards too its helpful by visually associating different colors for answers. I use a variety of different formatting techniques too for faster visual grokking/grepping of cards
Then I tried with the app Dr Moku that has mnemonics, took like 90 minutes until I started to get a perfect score.
Still takes spaced repetition to keep it in long term memory though.
I use Anki constantly to study Math (or really any technical stuff, but Math is what I mostly study). I would never study without it again - I'm still unhappy that I did an entire 1st degree in CS before I knew about Anki, and barely remember most of it.
The more I use Anki to study Math, the more cards I tend to make. I usually make a few different kinds of cards (usually as I'm studying a textbook):
1. Definitions - usually something like "What is Normal operator? [Define]", with the back being something like "A Normal operator is an operator that commutes with its adjoint". I might add a bit more detail and flair (depending on the context).
Sometimes it's a more complex definition, e.g. "What is a group [Explanation, 3 axioms]", with the back being an overview plus the group axioms.
2. Basic theorems/properties - no proofs, just something like "What kind of matrices always have property X", "Orthogonal matrices".
These are often hard to phrase right, since it might be far too ambiguous to remember 2 years from now. I try to use these semi-sparingly.
An easier example: "What is the project of vector U on vector V", answer: "<u,v>/<v,v>v". (Again, I'm omitting details here like saying "in an inner product space", etc.)
3. Proofs - I tend to use these a lot these days. I'll often either just make a card for a proof "Prove that a compact set in a metric space is closed".
I'll also often err on the side of adding a proof, instead of using a "thereom result" card like in my point 2 above. E.g. instead of asking what is the project of u on v, I actually have a card saying "what is the projection of u on v? Answer and prove". That way I can always reprove it in my head. I usually do this when the proof or explanation is short, if not, I might just split it into two cards (one asking the answer, one asking for the proof).
4. Calculations - I have cards for base calculations if the subject warrants it. E.g. "what is the result of this matrix multiplication". Or even simpler things - I realized while studying math that I forgot a lot of even trivial stuff from high school, e.g. how to factor quadratics using "complete the square" - so I have cards with a few examples of this that I need to solve.
5. I also have some basic facts that I want to memorize, e.g. "derivative of ln(x)" or stuff like that.
Note that while I use Anki extensively for Math, I actually use it for lots of other stuff too.
Aren't proofs going to be absurdly long? You might have a one sentence question, but it demands a 5+ line proof. That takes the longest to review the card though. I almost want to say a multicloze statement is better here, to prove individual parts of the proof. But then you get way too many cards, etc. It seems to contradict best practices of what most anki practioners emphasize.
https://math.stackexchange.com/questions/2111662/prove-compa...
"Prove that a compact set in metric space is closed" seems to be 5 or so major steps involved.
I suck at proofs and find that math is a really big weakness I have. I tried using anki for mostly math, but I still haven't reached that pivotal point where everything just makes sense.
For one thing, there are a few reasons to formulate things with smaller answers - one is that there's not always a logical connection between different things, one is to know them separately, one is that if you fail part of a card, you want to only fail that part - and you can't do that, so you need it separately.
The thing is, with proofs, they are logically part of a whole. They do flow logically, one part after the other, at least once you know the big idea - given the big idea, you should be able to do the rest of the steps by simply applying previous steps (usually).
That said, reviews of proofs do tend to take me longer, which is not ideal. And I do let myself "cheat" a bit with proofs - if I know the main idea behind a proof, and am fairly confident I can develop the rest of it (especially if it's a calculation only), then I might consider it answered. But I am fairly strict that I really do think I could develop it.
For example, the compact sets question was something I recently failed. Here's why: the main idea behind it is to prove that the complementary set is open, and the way to do that is to pick each point, define a ball around it and around each point in the compact set, then show how that proves every point has a ball around it.
Now I know all those big-level steps, but when I tried to remember how to develop it further, I realized that I wasn't sure why I needed the original set to be compact - why doesn't this work with any set? So I failed the card.
One other point - I do use a few custom note types for some math things. I sometimes use clozes, but I also have a note type for "Multipart Proof", which allows me to split up a proof into parts. I almost always actually use it to separate the "forward" and "backward" directions of an "if and only if" proof, since they are relatively separate anyway, but I do want to keep the card logically together.
I format my anki cards similarly for longer expanded question:
E.g.
- Question
- Short Answer (e.g. the conceptual idea and starting point for solving the proof)
- Long answer (the full proof)
What I tried to do instead, is reword each question slightly to ask a different part of the proof. Keep the long-answer the same, but modify the short-answer slightly.
I find from my experience the anki question/answer needs to be a one-liner though.
I use a yellow highlighted background for the short-answer portion. Its a basic front/back question/answer with some specialized stylesheets I made.
------------------------------------------------------------------
which allows me to split up a proof into parts. I almost always actually use it to separate the "forward" and "backward" directions of an "if and only if" proof, since they are relatively separate anyway, but I do want to keep the card logically together.
Are you chaining multiple questions / answers in one card? Something similar to glutanimate's video here? https://www.youtube.com/watch?v=ag4Hdnkig8U
Q1: "Prove that condition A iff condition B [Prove forward direction]" A1: "Assume A. Then [...] implies condition B."
Q2: "Prove that condition A iff condition B [Prove backward direction]" A2: "Assume B. Then [...] implies condition A."
Just that instead of generating this manually, I have a note type that allows me to put in the question once, then add the two answers, and it generates these two cards.
In reality it's a bit more complicated, because I can have more than 2 proofs, and can give each a title. E.g. sometimes you have theorems of the form "All of the following conditions are equivalent: 1) 2) 3) 4)." And then the proofs can be something like "1 implies 2, 2 implies 1. 3,4 imply 2, 1 implies 3" or some complicated thing like that. But these are pretty rare, it's usually just at most a 2 part backwards and forwards proof.
Are you essentially solving the same question in two different ways? (forward proof, and backward proof)
Or are they two unique questions each asking different things? (in the same related family of topics)
I'm working on improving my ability to write math proofs atm so I would find this helpful
> Are you essentially solving the same question in two different ways? (forward proof, and backward proof)
I'm talking of the standard "forwards and backwards" proof that you have to do to show two conditions equivalent.
I.e. if you have cond 1 iff cond 2, you need to both prove that cond 1 implies cond 2, and that cond 2 implies cond 1. (Or that not cond 1 implies not cond 2).
So it's often a similar proof, but not always.
Last 2 questions just related to just formatting cards
Does that render with inline-Latex on each card (e.g. are you using a latex anki plugin?)
Do you use powerformat pack plugin https://ankiweb.net/shared/info/162313389
The good news is that the new Anki 2.1 which just came out has built-in Mathjax support, so if you're using that, you can just start using Mathjax. Note that the default Mathjax code is not $ and $$, but this is configurable (though if I were starting from scratch I'd probably just use the default).
For all the examples you gave, I feel like those are the sort of thing that become so familiar in the process of working with those objects (e.g. spending long hours seeking proofs of theorems when I first studied them) that they’d be hard to forget, and I have trouble seeing how such cards would be helpful. I suppose if I just read through the textbooks and sought to memorize the definitions and proofs by rote then this would make sense, but I’ve always been told, and practiced, that the best way to learn the material is to find the proofs myself rather than just reading them straight through. And having done that, the key ideas of the proof, and especially the definitions (which became burned into my brain in the process of working with them) seem to last for months or years without explicit recall.
With language learning, it feels much more to me like rote memorization of an arbitrary mapping between labels in one language and labels in the other, so I find spaced repetition much more helpful.
I’m not trying to be dismissive here, just genuinely trying to understand. I would love to find a more efficient method for studying math, as it’s the main thing I do right now with my time and I expect at least several more years of it. If I’m missing a better way then I’d really like to know.
Thanks very much.
Now I'm not saying that I don't remember anything from the course... but I definitely remember extremely little. Even some of the "base objects" that we studied.
(It's not like I'm a mathematician who actively uses this stuff).
> I’ve always been told, and practiced, that the best way to learn the material is to find the proofs myself rather than just reading them straight through.
Let's be clear, I completely agree with this. I don't just copy into Anki - I study, and then I put into Anki.
In fact, just the fact of putting something into Anki tends to make me think about it much more clearly, as I decide what needs to be in there, how to rewrite the proof to be more concise but still understandable by me, etc.
I'm curious about this. Did your class require students to find many of their own proofs of key results, or was it more about regurgitating proofs from the textbook?
This was Calc 1 in a Computer Science program.
Basically, the final exam had something like 6 questions, most of them standard calculation or new proof questions.
But 2 questions were "prove this theorem that you learned", e.g. prove the intermediate value theorem or Weierstrauss' theorem or L'Hopital's rule or something. And answering at least one of these was mandatory.
The proofs were from a list of about 40 proofs that would be on the test. The effect was that you basically had to memorize 40 proofs before the test, or at least a good chunk of them.
I hated this at the time and though it was a total waste of time, but in retrospect, I think this was great way to force students to actually grapple with proofs. It was my first serious proof-based course (though I did proof stuff before in Linear Algebra and Set Theory courses).
And in retrospect, this is (part of) how I actually study today, so I guess I liked the idea.
"Property" cards can be very useful, even if only as a reminder. I can recall a card I had (back when I used Anki regularly) which asked you to draw a diagram showing how different types of convergence are related to each other (e.g., L2 convergence implies...). Just the exercise of constructing that diagram was very educational by itself.
One trick is I found it's best to design the cards so you can say the answer fast. You don't want to waste time verbalizing long asnwers. So my cards end up looking like this:
(Front of card) Evaluate: {'foo': 'bar'}.get('baz', 0)
(Back of card) 0
Or like this:
(Front of card) How to get [1, 2, 3, 4, 5] in lodash? _.___(1, 6)
(Back of card) _.range(1, 6)
That latter is an example of what's called a "cloze", where you show the full answer on the front of the card, except with one part blocked out. You can block out different parts of the answer to create multiple cards for the same question e.g.
(Front of card) How to get [1, 2, 3, 4, 5] in lodash? _.range(___)
(Back of card) _.range(1, 6)
What nonsense. You must have hung around insufferable people.
I only semi agree because this seems to be a phenomenon of an older generation. Newly minted PhDs are often much more proficient in programming, since they usually have received a much stronger education in that regard.
That's usually the easiest way to learn a new language.
Also, it's easy to get the bird's eye view of a language (say, React, for example), but when you're down in the trenches, you need to KNOW about the pedantic little details (like "class" vs. "className", "for" vs. "htmlFor", minutiae of React lifecycle, etc.)
To become a 'professional software engineer', one must learn to be a team-player within a group of persons tasked in building and maintaining a piece of software that will stand the test of time. Which requires a very different skill set. One can be a good SE and still be relying on auto-completion and inline help in one's favorite text editor.
Remembering the API of your languages definitely helps, but actually building softwares that will be used by real users, for years, that's what makes you a 'professional software engineer'.
Usually, a programming language (or an API or whatever) has some core part which you use daily. So, no need to memorize anything actively. Yes, sometimes you write something and wonder "Is there an easier or more idiomatic way to do that?", then you will search in the manuals or on stackexchange and you see how it's done. If you are curious (which I hope), you will maybe also check WHY it is the easiest resp. most idiomatic way. Again, no need for active memorization. Then there is the part of the language or API that you rarely need and that you don't have to memorize anyway.
To be honest, I am completely speechless. Flashcards? To memorize programming manuals? I know people who use flashcards when following crash courses to qualify as Cisco engineers or whatever. But for programming???
Part of how I got the job I got (an amazing dream job) is because the interviewers were flabbergasted seeing me live-code flawless idiomatic code like it was the back of my hand. Difficult to achieve that without SOME sort of systematic study. Most master pianists don't get there by just doing lots of casual play.
I should also mention, one of my main language is kdb+/q. Try mastering THAT without flashcards ;)
Could you explain in some detail how this works out in practice ? For example with someone learning JavaScript or Python ?
I created cards by going through this excellent free online book (I skipped chapters I wasn't interested in): http://exploringjs.com/es6/index.html
The process of creating cards: (A) read a paragraph. (B) make flashcards for everything new introduced in that paragraph. (C) goto A.
As for B, I would take great pains to make the cards as terse as possible while still drilling the concepts. Over-verbose examples should be rewritten more tersely (and tested in the browser to make sure you didn't screw up).
For example, from the first paragraph of Section 4.1 I might make this card, among others:
(Front) Evaluate:
var x = 0;
function f(){ if(false) {var x;} return x; }
f()
(Back of card) undefined
(Notice how I distilled the much-more-verbose examples from that paragraph down to a core that illustrates the key point.)
If you're serious about this, it'll take a lot of time. I used it to crash-learn basic kdb in about 1 month, but that required spending ~4 hours/day that whole time. Making cards is a skill in itself, you'll get better at it over time (a lot of my early cards are way too verbose and sometimes I'll rewrite them now that I've gotten better at making terse cards)
I cannot believe that you are following such a strange approach to learning programming. In fact, I believe that you are using Anki for something completely different than what you are claiming here. You are not making flashcards and you are not memorizing the answers. You are making quizzes and you are using Anki to check whether you are able to solve them. At least, that's what I hope.
But in your own post you point out that flashcards can be used for quizzes as well?
I think you have this weird idea that flash cards are only good for memorizing the things written on them.
That's a really limiting, and false, idea.
A flash card is just a pairing of a specific question with a specific answer. How you use that simple framework is up to you.
I used them for trig identities. That was straight memorization.
I also used them for proofs. As in 'Prove every edge in G^k is a walk of length k in G'. Then I'd work through the proof, and check my answer against the one on the other side. That's not memorization.
It's still flashcards though.
I like the unit test analogy - agree 100%.
For what it's worth, if I were to go back in time and take the class again I would add many more cards (perhaps up to 10 times more) and also improve the existing cards. My background in measure theory was far too weak for the class. I passed, but I don't feel that I knew the material very well.
So I'm curios, if you cram a piece of knowledge that is so interconnected as math is in flashcards and you rote learn all the definitions, theorems, proofs and examples - are you then capable of seeing the connections between them? What happens at the exam, if the professors asks you to prove a new lemma, where you have to combine previous knowledge, does that work?
Also, some proofs are pages long. Do you put them in one huge flashcard?
Since I've never use Anki succesfully for math, as I said, I'm keen to hear from someone who has.
In karate we teach some forms we call kata. When I teach these, I like to cover the details slowly at the beginning, break for other stuff, and then come back to it at the end to test their memory because it's long enough that short-term memory will start to degrade and they'll have to actually work at remembering it (and thus identify the parts they didn't really quite get).
It's very obvious to watch in realtime. It's a waste of time to just work on teaching the kata for 2 hours straight because they get exhausted and lose focus. It's just as effective to teach it for a half hour at the beginning as long as I have a 10 minute review at the end to solidify what they learned. I usually think of it as three separate practices -- warming up the form, practicing the form, and executing the form.
Warming up means going at half speed with the intent being to refresh the memory. Practicing means going at 70% of full speed to help get it into active memory more solidly. Executing means going at 80% of full speed and focusing on checking muscle memory (video works great) under conditions of some mental stress, and also actually developing the techniques and theory further.
To get back to your point, I see no reason why you couldn't make your card require all three types of reviewing something. But I am not sure if the time constants on forgetting practiced skills is different than memorized facts. In karate your deeply practiced skills are in muscle memory (or for you perhaps in your most accessible memory with the math details you don't even realize you're using which are not known to most people). Having stuff in muscle memory is the bare minimum required to actually move further.
You can't learn karate from reading a bunch of articles and watching karate videos. You have to actually practice it to reinforce the memory and build new connections between different concepts. Does that sound familiar to how you think about learning math?
Put another way: math isn't really about memorization, either of behavior patterns or of facts. That's why I've been confused and somewhat skeptical about the utility of flash cards for learning higher mathematics.
Step 1: Read about stuff people are doing.
Step 2: Read between the lines to understand how it fits into other things I already know about.
Step 3: Evaluate based on my intuition whether the fit is reasonable. Since the data is presumed real, if the fit is bad it usually means I didn't understand the details of what they did. See if I can make the fit with other things I know coherent.
Step 4: If I can explain the fit coherently, consider what problems might be solved by using that connection.
Step 5: Research how that problem is normally solved and why.
Step 6: Go back to Step 1 and keep going until I find something that is actually solved better using my weird idea than it is solved currently.
I am terrible at memorizing, and if I am in Step 3 or Step 4 or Step 5 it's a real roadblock if I'm trying to understand why I can't harmonize the reported data and my understanding and it's because I've forgotten which sites are interstitials in a fluorite lattice. I know the information I need, but now I have to go look it up. Of course this is why people have reference materials, but it's definitely a speed bump.
The important aspects of the work up there clearly aren't about memorization, but it sure helps me actually do it in practice. I really wish I were better at it.
Another thing that this made me think of was using it to remember student/coworker names. Remembering my unreasonably numerous cousins' kids' names would also be nice.
I mean, on the surface level that's true. But obviously we could reductio ad absurdum this claim - would a mathematician be able to work if they lost all their memories every day? Clearly not!
It's something of a matter of how good is your memory, plus how actively you use it. How many people who complete PHDs can still prove the PHD 10 years later? Not many. Which is not to say that you can or should use Anki to learn something as complicated as a PHD dissertation, that clearly won't work. But when learning a new topic, it's a very helpful tool, and it makes sure that even if you now focus only on linear algebra, you'll still recall at least the basics of, say, set theory, which most mathematicians who don't actively study probably don't use much.
> It's nothing like what higher mathematics demands, which is much less about rote memorization and much more about deep understanding of the intricate interconnections between a comparatively small number of concepts.
Well Anki certainly won't help you actually do higher math :) But I find it is surprisingly good at making these weird connections, because in the middle of learning say modern algebra, you'll suddenly need to recall things from linear algebra, and suddenly see interesting new connections. Or things from real analysis, which will make you go "hmmm, so that's why a field is defined this way" or something.
Of course, that's half for exercise instead of just memorization. And obviously it's less necessary from a memory perspective pretty quickly, I can go at least many months without doing a kata and still rapidly pull it back into working memory from a video review (during those times in my life when I couldn't practice regularly) and a few times through myself.
But if it's not in active memory I definitely won't be improving it. Just reinforcing the memory and getting a bit of exercise.
But specifically: > [...] I'm curios, if you cram a piece of knowledge that is so interconnected as math is in flashcards and you rote learn all the definitions, theorems, proofs and examples - are you then capable of seeing the connections between them?
Well, I wouldn't think of using Anki as rote learning things. A basic principle is that you must understand (at least in something like math) before you put it in Anki. I wouldn't make a card without first understanding what it says. In fact, the very fact of making a card will often make me understand the proof much better, just by trying to write a more minimal and easy flowing version of the proof, or trying to put in a mnemonic or visualization that will make the proof clearer. (Btw, even after doing this process, I still find that I often can't recall the proof easily even 4 days later! Such is my memory, at least. I can sometimes reprove, but not always.)
Hopefully, if the exam asks to prove a new lemma, having lots of examples in your memory of how to prove things or how to solve exercises in e.g. linear algebra, will make it much easier to do it.
Look, I'm no scientist, but the science here is pretty solid - active recall helps a lot. It's essentially what lots of students are doing when studying for tests, only (scientifically shown to be) more efficient - solving example problems/proofs, etc. And it has the benefit of being inside a system that will hopefully keep the knowledge alive even in 10 years, not just for the exam and that's it.
> are you then capable of seeing the connections between them?
This is probably the best hidden feature of Anki. Because I often will get basic cards surfacing a few months after learning them, I will often find connections that I didn't think about (or couldn't know) the first time! I've even had some cases where I will recall a definition or theorem that I wrote from the beginning of the study, and realize that actually, I got part of it wrong! And now that I know a lot more, I easily see "wait, that can't be right" and dig deeper to discover what was my misunderstanding!
Well, that is what I actually did with Anki in university. For any lecture, I would go over the material, identify the important snippets, and make them into Anki cards. Creating the deck itself is very productive work because to identify the cards and make them small enough, you have to have understood the material. If you just copy the entire page-long proof in, you haven't understood it. Anki forces you to break it down because a card like that is useless.
So if you're already making your own notes why would you want flashcard software?
- It optimizes reviewing, ensuring you look at forgotten cards every day, and easy ones only once a year, instead of randomly poring over the entire set of notes and hoping to stumble upon the forgotten ones.
- It allows higher card quality, e.g. I can paste screenshots of visualizations instead of scribbling them down. My language decks have audio pronounciation, a paper medium does not support that.
- It allows higher card volume, I can't fit 10000 cards in a notebook but I can do so on my phone. Especially not high-quality cards with images in them. Of course nobody even considers fitting 10k cards on paper because reviewing such a collection is not feasible without spaced repetition software (see two paragraphs above).
- Its much easier to pull out my phone and do some reviews in the car or public transit than to do the same with a notebook.
This was quite eye opening to me when I first heard of it. Apparently, our long term memory is virtually limitless. You never truly lose something you once had learned well.
Another fact about memory that I found equally interesting: memory is not a "thing" but a process. When you recall something, you are actually reconstructing the memory from various factors associated with it, pretty much like how a paleontologist might reconstruct the image of a dinosaur from fossil remains.
There are startling experiments in the area. Take a large set of pictures (it has been done with sets of up to 20000 at least). Take half those pictures and show them to subjects, one at a time, giving them a few seconds to look at each picture.
Later, take the set of pictures you showed them, and pair each with one of the pictures you did not show them. Shuffle that set of picture pairs, and then show the subject the pairs sequentially, asking them for each which picture of the pair they have seen before.
On a test that used 20000 pictures, with the recognition test a day and half later, subjects got 80% right. If instead people had just been asked to recall as many pictures as they could, most people only be able to recall a tiny fraction of them.
Here are a couple of papers in this area:
https://www.gwern.net/docs/spacedrepetition/1973-standing.pd...
https://www.ncbi.nlm.nih.gov/pubmed/18787113
> Another fact about memory that I found equally interesting: memory is not a "thing" but a process. When you recall something, you are actually reconstructing the memory from various factors associated with it, pretty much like how a paleontologist might reconstruct the image of a dinosaur from fossil remains
This is sort of illustrated by a thing called the Baker/baker paradox. Show people a photograph of someone, with a label that says "BAKER" attached. Tell half the subjects that the label means that the person is a baker, and tell the other half that the label means his name is Baker.
Later, show the subjects the photo but with the label removed, and ask them what the missing label had said. The people given the job story will be much more successful at remembering this than the people given the name story.
The name "Baker" has very little associated with it in most people's minds, whereas the job "baker" brings up associations with all kinds of delicious treats, and maybe childhood memories of wonderful smells permeating the house as your mother baked in the kitchen.
So when you are told the photo is of a baker, all of those things that baking is associated with in your mind get associated with the photo, and you've got more to grab onto mentally when trying to recall the label. These may be weak associations, but they still beat out the name "baker" which for most people has no extra associations.
Anyway, we don't just reconstruct the memory to recall it. We also might edit it and save the changes. This has serious implications for the criminal justice system when dealing with human witnesses.
If an investigator interviewing the witness says anything that suggests events happened different than the way the witness remembers them, there is a danger the witness' memory will change to match the interviewer's version. The witness will not know this is happening, and genuinely believe that the updated memory is what really happened. These aren't always minor updates...they can be big, like in a confrontation changing who drew a gun and started shooting.
I don't have a link, but I've read of experiments where researchers got parents or older siblings of some adult subjects to mention at a family gathering some amusing/embarrassing incident from the subject's childhood--a totally made up incident. Later, the researchers found excuses to question the subjects about that incident, and the subjects "remembered" it, and not only the details that had been supplied in the made up story. They had filled in complete details about the incident and the things leading up to it and following it.
The trick is investing some time to build a personalized memory system, then use the system to remember other things like passport number, credit card , phones etc. It might not be attractive to most people because today we have smart phone to help us. But for learning new knowledge, combination of both space repetition and memory system is quite interesting. Here's what I did: I use a Anki alternative called Memrise[3] to build a Major system. (I also have Anki installed but just prefer Memrise). Then I use Major system to review the concepts I've learned. Major system here is the equivalent of Anki as a tool for short term place holder of space repetition, not directly used for learning. I found brain Anki is better than smartphone Anki/Memrise although I built former Anki with later Anki.
Come on fellow hackers, hacking your brain is very rewarding
[1]https://artofmemory.com/wiki/Method_of_Loci
I considered working on this, but I'm just not excited enough about remembering. Thanks google. Oh and Einstein said (according to Shaq) you should never remember what you can go lookup.
“Graduated Interval Recall - Dr. Pimsleur’s research on memory was perhaps one of his most revolutionary achievements. He discovered that if learners were reminded of new words at gradually increasing intervals, each time they would remember longer than the time before. He documented the optimal spacing for information to move from short-term into long-term, or permanent, memory. This theory is at the base of all the Pimsleur programs.”
The statement does not deny that actually doing stuff is important - "work steadily". However, these are just empty words to someone who tries to become a genius by hitting the books first.
My advice (yes, I do see the irony here) in this age would be to postpone seeking advice or reading about a topic as long as possible. As a result, your common sense sharpens and you may even come up with fresh, creative ideas that others perhaps didn't have.
> postpone seeking advice or reading about
> a topic as long as possible
Oh gosh, the number of inefficient solutions, horrible architectures, brain-dead encryption systems I saw, because of the people who did not bother to open a book.To come up with creative solutions you need to have a base for said creativity. I.e. to connect the dots in original way you need to have the dots already.
I have nor proof, but I suspect that the number of useful solutions created by people who know nothing about the field is close to zero.
Somehow I doubt one would see much further when instead of climbing onto the shoulders of giants they prefer to stay in the pit of their own ignorance.
If you hadn't come across horrible architectures you would have learned less about good ones. It would be nice if this all happened inside of one person, that's what the parent is suggesting.
Growing up, I (falsely) internalized that I somehow had a hard time learning languages. However, with the help of Anki, that has an algorithm based on SuperMemo, I realized that this wasn't the case - just that the traditional textbook methods weren't for me when it comes to cramming in "arbitrary" information.
While living in Japan, I used Anki to supplement my recognition of kanji. I averaged roughly 7 minutes of studies for a year, internalizing the meanings and readings of roughly 1000 characters with a 95% retention rate.
Judging from my peers, the only ones that managed to pick up this volume were those that studied the language full-time. Of course, they learned the language overall at a much higher level than I did - this methodology purely focused on the recognition aspect.
Naturally, I got to put the characters to use living in the country, and I also spent time making up mnemonics for each character. Your mileage may vary.
I'm not a student of Japanese, but AIUI there are pictographs and ideographs amongst the characters, presumably these are effectively already mnemonics?
However, most characters are composed of a few common components, called radicals, which can sometimes provide hints about the meaning. For example, the Chinese words 海 "sea", 波浪 "wave" and 渴 "thirsty" all contain the water radical ⺡. Similarly for 丝绸 "silk" and 缠绕 "wind around", which contain the thread radical ⺓.
Personally, I don't use any mnemonics, but I know someone who does, and he'd assigned each radical a memorable representation (e.g. the thread corresponds to Spiderman) and then he had a story linking a word to the components, so that 丝绸 would be about two Spidermen, one of which wraps himself in silk to use it as a ghost costume.
童 means juvenile. Imagine someone who is so childish that they jump on top of their computer in anger when it blue screens. I've always gotten this flashcard within 5 seconds with Anki, and generally chuckled to myself as well.
脂: Meaning: Fat. Consists of 旨 (tasty) and 月 (moon). However, mnemonically, 月 occurs in many characters referring to "flesh" of some kind, and as such is what I often use as a mnemonic cue. This creates the quite natural mnemonic cue of "tasty flesh". As such, when seeing this kanji, my thought process when repeating the character goes something like "the tasty part of flesh - the fat!".
> while pictographs are pretty and easy to explain, they only make up around 5% of all characters. Phonetic-semantic components, on the other hand, make up almost 80% of all characters
Following on from that, maybe such question answer sets could be automatically generated from the semantic web? A simple example would be a question/answer set about capital cities, but could one pick an arbitrary subject and manufacture a list of questions about it?
I am working to solve exactly this. A form of learning where the learning happens due to interaction between a bot and a human. Machine teaching humans basically. Been working for over 20 months. Will be releasing within two weeks. :)
First you need to understand the subject, then you can formulate useful flash cards, then you can work on remembering them.
There are so many random features like the sleep tracker (https://www.supermemo.com/help/sleep.htm) that don't really make much sense to have but are there anyway.
There's also a web version if you just want flashcards that's mainly focused on language learning. They sell some courses and you can add your own cards too.
The biggest selling point for me is the incremental reading (https://www.supermemo.com/help/read.htm) feature. It's the only way I can manage to keep track of so many articles that I find interesting, and is vastly superior to leaving hundreds of tabs open or a bunch of bookmarks I'll never look at. It's superior to instapaper,readitlater etc because I don't have to decide what to read when I open the app, and I don't have to worry about forgetting about the article if I stop in the middle of it.
If I see anything remotely interesting, I just chuck it in Supermemo, and I'll see it eventually. If it's really important, I'll set its priority higher so I see the article sooner.
If I'm doing research on something and have 15 tabs open, all 15 tabs go into Supermemo, and will eventually get whittled down into flashcards. Start with an article -> extracts -> smaller extracts -> cloze deleted flashcard.
Long comment chains on Hacker News? Supermemo. Youtube videos? Supermemo. Email? Supermemo. Images? Supermemo.
I check my RSS feeds once or twice a week, grab all the interesting articles, import into supermemo, and I'm done.
Supermemo for me replaces: Evernote/OneNote, most bookmarks, Anki, and various todo list apps.
If I just wanted to make flashcards from set material, I'd honestly use Anki, because of the mobile apps. It's really easy to do a few repetitions when you have downtime through the day.
Every person I've shown this app too doesn't really care about it, and I don't really know why. If I had to guess, it's probably because the UI is horrific. I can effortlessly keep up with so much information, and it takes an hour or two out of my day.
When importing articles, does SuperMemo store the original URL? How about the layout of the original article, e.g. photos or diagrams in addition to the text? Is it IE-only or can it work with Firefox to import multiple tabs?
But in general, I get all the photos and diagrams too. URLs are stored, and you can mark up the article further as well for easier searching later. An example: https://www.supermemo.com/help/images/f/f5/Incremental_readi...
Supermemo seems to be heavily integrated with gecko/IE, probably due to age.
http://www.connectedtext.com (Windows)
https://www.devontechnologies.com/products/devonthink/overvi... (iOS & Mac)
Man, does't really work that way? When I learn something, like ML, I need the knowledge to sink in, but most of all I need to experiment, to test, to see how it works in practice. I guess the incremental reading may work for something like learning anatomy etc., but I doubt it would help me with more complex abstract concepts.
If I could only give one advice to someone about improving their learning skills, it would be to learn about spaced repetition
Now I use Anki almost daily for learning programming, math, vocabulary, and retaining books I've read.
On books, I originally wrote a script that scraped the Kindle highlights page and converted them into a file that could be imported into Anki. I'd Cloze delete passages and review maybe 20 a day. That practice was so beneficial that I've since started developing it into a standalone product called Readwise. [1]
Readwise doesn't yet incorporate hardcore spaced repetition and active recall principles, but it will soon.
[0] https://alexvermeer.com/anki-essentials/ [1] https://readwise.io
1. Have you considered some way to add Instapaper-like parsing and highlighting into your service? It isn't cheap paying for two subscriptions with Instapaper reverting back to a $30/year subscription for my internet highlighting/notes plus your subscription.
2. From the website, it seems like you already have spaced repetition. What are you hoping to add?
3. What spacing repetition algorithm are you using? SM?
Just looking at it briefly, it appears to be pretty nice.
FWIW I read somewhere that Anki started off as an Emacs mode, initially, though the only source I could find now (quickly), is this:
https://news.ycombinator.com/item?id=10925971
Edit:
The Web archive helps (as always):
http://web.archive.org/web/20091001153225/http://ichi2.net:8...
Spaced repetition does work though, I used a tool called Anki which has a free online sync service and free apps for every platform (bar iOS, it costs £15 on that platform).
Internally, Anki’s spaced repetition system is based on an older version of the SuperMemo algorithm called SM2
Exactly what I thought. Some parts (10%) are very interesting, but it contains so much stuff I don't want to remember...
https://www.supermemo.com/articles/paper.htm
I thought it would be interesting for me to do this method while I'm studying a scientific paper. Any thoughts?
As for using it for scientific paper study - depends what you expect from it. Spaced repetition is great for remembering and retention of facts. When I'm reading a scientifi paper, I rather struggle with the basic understanding of it :)
Scroll down to the heading "Using Anki to thoroughly read a research paper in an unfamiliar field".
I learn a piano piece, memorize and internalize it, but then if I stop playing it for a few weeks, it completely vanishes from my head. Super frustrating, it's like starting over every time.
On the other hand, I have very good auditory memory -- I can "hear" and recall music in my head without problems. But that's unhelpful to me when I try to play music.
Repeat the same process when you have your piece memorized. Then play your piece from memory but hands alone. You will build up the muscle memory required to keep the piece in your fingers, rather than your head.
But eventually I'll move on to the next piece, and wind up forgetting to re-visit the other one for a few weeks or months. Gone!!
Maybe adapt your practice to the forgetting curve, revisit a piece the next day, then in 3 days, then in 7 days, then in 2 weeks, then 1 month, then 3 months, etc. If ever you mess up the piece, then it's back to 1 day.
Does anybody know if the original creator is still in charge? Supermemo.com got reworked really heavily a couple of years ago and I wondered if he may have sold his company, or maybe just hired a team to make some apps
How often should repetitions be spaced, roughly speaking? Is there a rule of thumb?
Nothing groundbreaking. I'm sure other people have done the same things out of sheer efficiency - no need to keep going over the easy cards.
Study 10-20 new facts today. Review them afterward (same day). Once you feel you “know” them push them to tomorrow.
Review old facts. If you still know it, approximately double the time until you see it again. If the last review was 1 week ago, next would be in 2 weeks.
If you’ve forgotten it either restart it (you really don’t know it) or use some easing factor to schedule it.
Real answer: get Anki and let it do the work. Tweak it as needed.
1. It takes discipline to understand the material properly before attempting to just bang it all in Anki, but learning directly from Anki can be miserable, so it really is best to try to grasp it fully before going near Anki
2. Creating the right questions can be difficult - sometimes I found myself able to regurgitate the answer but other tests proved I didn't really understand the meaning. One way to approach this is to test different aspects of the answer, or to add the inverse of the question. Still even if you don't grasp the meaning properly just having a rote answer in your head can improve your capability
3. Life often gets in the way of the discipline required!
> "The winter sun sets in mid-afternoon in Kolobrzeg, Poland, but the early twilight does not deter people from taking their regular outdoor promenade"
I find titles promising a specific piece of useful information combined with longform, author storyline based content to be one of the most fustrating things about reading traditional journalism on the internet. A form of bait and switch.
No proper headings.
To hell with that. I won't ever know what they're on about.
Journalism students spend so much of their time doing pointless writing exercises, they feel like they should continue with it, as if their reputation depends on it.
In the modern world the opposite is true - attention spans are short, you must get to the point.
A similar thing is true in video - I can't stand vloggers who dance around or have to explain the whole history of the subject before getting to the point.
I blame Google - they incentivise long articles with lots of keywords and longer videos.
For example: this article has been voted to the front page of HN, which is more than thousands of terse, AP-style inverted-pyramid news articles can say.
I used to cover-to-cover it pretty regularly, and these long form articles/headline combinations are great in that situation.
Sure, it's not great for the internet. But I don't think it's a feature of "internet journalism"
I've completely stopped reading past the first sentence of articles that begin like this, which is a lot of articles recently. If I wanted to know what people ate for breakfast, I'd use facebook!
> A form of bait and switch.
It's an article from Wired _MAGAZINE_.What do you expect? A terse jargon-filled exposition of the algorithm fit for graduate students?
It's perfectly fine to not appreciate the style of the author, but to call it "bait and switch" is a bit much.