Last week, John Pasden wrote an introduction to spaced repetition (you can read mine here). He and I don’t quite see eye to eye on the issue, so I thought I’d be able to pick a fight. Alas, I agree with his three main points:
- SRS tends to appeal to technical people (he cited programmers specifically, but I strongly suspect it extends out to lots of engineers, scientists, etc.).
- Non-technical people tend not to use SRS because they don’t like being “spoon-fed” knowledge.
- SRS technology is being built into an increasing variety of study tools (he listed Skritter for Chinese and Smart.fm for Japanese as current examples), and eventually most everyone is going to benefit from it in one way or another.
I wish I could more strongly argue that everyone must use SRS, but I can’t, because I accept that what John says is essentially right — it doesn’t appeal to non-technical people. That doesn’t mean that you don’t need repetition, though.
Memorization isn’t a four-letter word
Memorization has gotten a bad rap. When we think of memorizing things, we tend to think of mechanical, rote memorization forced upon students by angry, over-corseted 19th century schoolmarms. Memorization, though, if don’t right, is simply priming your brain for processing material that you’re going to encounter frequently. Memorization has and will continue to be an integral part of your learning experience, whether you realize it and call it memorization or not.
An example: 9 × 9 = ???
You probably know the answer to this question, and you probably know it simply as a fact, rather than something you determine through calculation. If your elementary school experience was anything like mine, you drilled multiplication tables in about 3rd grade until multiplication of at least the numbers 1-10 became second nature. You didn’t need to do any math to know that 9 × 9 = 81 — you just know.
You, of course, have memorized the multiplication tables. Why would you do that? After all, there are plenty of calculators around, not to mention relatively simple ways to calculate the answer in your head. The answer is speed — by just memorizing that the product of two nines is 81, you can skip all of the mental calculations and just produce a number. This is important because multiplication is a math skill that you’ll continue to use throughout your math career. Increased efficiency in the most basic skills translates to greatly increased efficiency in more difficult skills that build upon the basics. Imagine calculus if you had to work out the answer to every addition, subtraction, multiplication, and division operation each time you encountered it.
In any field where advanced skills build upon basic skills, there are benefits to be had from simply memorizing things at the lower levels so that you can deploy them with speed at the higher levels. Language, of course, is no exception. A simple example is learning Chinese characters. Of course you can look each character up in a dictionary each time you encounter it, but that’s a hellishly tedious process. Instead you memorize that 及 is pronounced jí is means “and,” so that each time you encounter it your brain immediately knows the answer to the question the character poses and moves on.
Repetitio est mater studiorum

Repetition is the mother of learning
Memorization is of course accomplished through repetition. The more you repeat something, the better it sticks in your brain. You might need more repetitions or fewer repetitions depending on who you are, but very few of us can get away with no repetitions at all. There are plenty of other factors that determine how well you’ll remember things, but repetition is a big one, and one that you can control directly.
Repetition works in building memory because of the underlying way that you brain builds skills. There is an increasing body of research (and a pretty interesting book, Daniel Coyle’s The Talent Code) that shows that our brain’s white matter — stuff called myelin — wraps often used neural pathways and increases the speed at which transmissions along the pathway are made. Because such myelin growth is spurred by the activity along the neural pathway (and, seemingly, nothing else), its only by repeatedly using that neural pathway that its transmission speed is increased.
Our brains are better at what we do often — both physically and mentally — than at what we do infrequently. Repetition is the key to the underlying neurophysiological system by which we become proficient at something, from swinging a tennis racket to speaking Swahili.
There’s no escaping repetition
Two interesting comments regarding SRS by non-SRS users help to highlight this. First, by Brendan O’Kane on John Pasden’s SRS post linked above:
I’ve never made much use of SRS for the same reason I never used flashcards — I’m basically a lazy, undisciplined learner. Anki and applications like that seem to be sort of like Getting Things Done systems — just great, if you’re the kind of person who can use them, but no good to people who can’t. Or at least me.
Then again, the way I’ve learned without computer aids does roughly resemble SRS: I’ll read something, have to look up a character or word, and then either remember the character or word, or not remember it, get irritated with myself for not remembering it, and remember it the second or third time.
The second by JP Villanueva on my post about how I learn foreign languages:
I don’t do Anki (or flashcards at all for that matter) because the languages I study are roman alphabet and usually cognate languages, so I find re-reading (x2 or 3) to be sufficient (after the look-it-up stage, of course). Short stories and fables are my genre of choice.
Both of them are tremendous language learners, and neither of them use any formal spaced repetition, but both of them nod to repetition as being part of their study. I suspect that if you ask almost anyone that has achieved a high level of skill in any field how they got there, repetition will be part of the answer. It’s just something that comes with having a normal human brain.
So, I … uh … don’t need SRS?
You don’t need SRS, just like you don’t need to eat broccoli. Sure, its good for you, but you can get the same nutrients elsewhere, and the nutrients are what really matter, right? Some people totally love broccoli, though, and so for them getting it just makes sense to eat what they love and reap the benefits.





{ 1 trackback }
{ 9 comments… read them below or add one }
Hmmm… I don’t think anyone will argue against repetition. I certainly won’t.
Tell me, though, now that you’ve mastered your times tables (through the 12s?), why don’t you keep going with SRS, putting in higher and higher numbers?
No, nobody would argue with repetition, and since SRS is just repetition done with an actual understanding of human memory, nobody should argue with SRS, though plenty do for a variety of (probably totally valid) reasons. The point I was making (and probably should have made more explicitly) is that if you’re learning you’re either: 1) using an SRS; 2) doing the same thing yourself, almost certainly less efficiently; or, 3) not retaining the material.
The answer to your question is diminishing returns. I think that applies to all learning, though.
The question of efficiency is actually not so simple, because when it comes to learning a language, there are so many dimensions. I think this is why SRS appeals mainly to programmers: they often see language learning in terms of data. If, however, you’re learning a language for the purpose of human communication, you may find time spent with SRS utterly joyless. On the other hand, time spent using the language to talk to people is (1) the realization of the original goal, and also (2) inefficient reinforcement of all learned material. If time spent on SRS is time which could be spent talking in the foreign language, or reading in it, then the law of diminishing returns takes on a new meaning: how soon can I get away from the memorizing and just be free to learn through pure immersion?
Um, no, the question of efficiency (purely in terms of memorization efficiency, of course) is that simple. What you’re talking about is whether or not that efficiency is a good thing. That’s totally debatable.
I think you’re mischaracterizing programmers (and a lot of other people). I don’t know anyone learning a (living) foreign language whose goal is not human communication. I’m sure they exist, maybe in droves for all I know, but I don’t know any of them. It’s just a question of how you prepare for human communication.
The metaphor I tend to use internally isn’t data processing but rather one of an athlete lifting weights. Weight training is not sport in and of itself for most people, and everyone recognizes that time in the weight room does not directly become skill on the field, but it does provide the core capabilities necessary for success on that field. It’s not the only way — you could just out onto the field and get creamed for a while (the “100% immersion from the beginning”), and build up your muscles that way, or roll logs up hills and chop wood (other, less efficient forms of memorization) or whatever — but it’s a pretty efficient way.
I’m talking efficiency of the whole package, including putting what is learned to use. Memorization is only part of the equation, and memorization efficiency, it would seem, is not a big concern for the vast majority.
As for mischaracterizing programmers… I call them like I see them
It’s not that programmers don’t plan to use what they learn for human communication, it’s that “proper” accumulation of data through a good system is a major part of the enjoyment for them.
May I jump in?
My girlfriend is Taiwanese and most of our friends are Taiwanese/Chinese (because I have no friends) but I’ve noticed that when I “immerse” myself and rely on conversations and company for all my Chinese studies, I find that I may learn a lot of new words, but I may forget some old words as well. Maybe it’s because I’m not a genius, but I really need to do my homework if I’m going to keep those words in memory and SRS is the most logical way to do that. (I don’t need to go through 2,000+ cards every day).
John B. made the analogy of weightlifting. As a musician, I’d like to share another one. As in weightlifting, there’s preparation, and then there’s the act. Obviously practice is necessary to be able to perform well. However, there is the (too often overlooked) danger of practicing for the sake of practicing. It’s easy to lose sight of the goal. If you become obsessed with technique and don’t give any thought to musicality or feeling, at best your performances will be dull and mechanical, however polished.
I think this echoes what John P. seems to be stressing about immersion. If you isolate yourself in a room and force-feed yourself vocabulary, not only do you never get any real practice but you have no context; you’re in danger of loosing sight of your ultimate goal.
The thing is, I don’t see “SRS” as part of this argument (practice vs. implementation) at all. Its point, like John B. said, is to help you become more efficient at the practicing part of the whole package. The learner needs to understand the importance of both aspects (practicing and performing) and try to divide his/her time appropriately. The important thing is to make sure that your efforts in practicing support the performance. As in music, nobody can calculate the ration between the two aspects; each individual needs to work it out for his or herself.
Finally, I personally believe that us Westerners spend too much time theorizing about this stuff anyway (of course in this case I am guilty. doh!) rather than getting our hands dirty so …算了.讀中文吧!
Sorry for that last bit, I just realized that this blog has nothing to do with Chinese specifically; followed the link from Sinosplice.
John said,
“As for mischaracterizing programmers… I call them like I see them
It’s not that programmers don’t plan to use what they learn for human communication, it’s that “proper” accumulation of data through a good system is a major part of the enjoyment for them.”
I totally identify with that. It also explains why, when excitedly trying to “sell” the SRS concept to my non-programming friends, I’m usually met with glazed eyes.
Oh well, not to worry. At least now I can get back to tweaking my Anki model for optimal performance and doing a few more reps..
Ryan,
I think what you bring up at the end of your comment is something that I should have pushed more strongly: SRS is just part of a “balanced breakfast” of study habits. Everything — reading, writing, speaking, and listening — has its place, and neglecting any of those things is only done at the learner’s peril.