I have been using anki for almost ~3 years now to study Korean vocabulary, sentences, and Japanese kanji. I'm also a software engineer for my day job. I've also written about anki. [0]<p>I don't see the value in memorizing programming -syntax-. It's irrelevant to me to remember how to open a file in ruby or do a specific command- that's what search engines and then my personal wiki is for.<p>If I worked -only- in ruby, then I'd likely remember those specifics much more, but since I hop around with rust, python, c#, clojure ... depending on our clients, there's no way I'm going to remember stuff like that for every language. Especially since languages tend to get updates and changes!<p>I would use anki to retain knowledge of stuff like more complicated data structures. Right now, I just search for what I need, then toss it into my personal wiki folders. I can then use notational-fzf-vim to rapidly fuzzy search my markdown files. [0] I keep these synced across computers with a selfhosted nextcloud instance.<p>[0]: <a href="https://andrewzah.com/tags/anki" rel="nofollow">https://andrewzah.com/tags/anki</a><p>[1]: <a href="https://github.com/alok/notational-fzf-vim" rel="nofollow">https://github.com/alok/notational-fzf-vim</a>
What's the point? Programming language rigmarole is well on its way to being automated. It's better to memorize algorithms. Make flashcards of Knuth, not stuff that IDEs autocomplete for you anyway.
Is there a benefit to trying to actively memorize the syntax/semantics of a language rather than just looking it up when you need to know something, and then passively memorizing the parts you use often?<p>Also a huge component of memory is contextual cues, which is why people find it so hard to code on a whiteboard vs. being at their normal computer/keyboard.
I tried spaced repetition for a few months, but I found that I wasn't actually learning anything, I was only remembering facts. I'm not sure what I expected, but when I "learn" something, I grasp the "shape" of the concept...how it fits with other things...where its edges are...where parts of it are unexplored etc. This only comes to me by using the thing I'm trying to learn, not by injecting random facts into my memory.<p>If anyone has had similar experiences, I've found the best way to learn has been writing about things that I use, as I'm using them. The rule for writing in that way is only write what you've come to understand...don't just copy text that is "useful" from another source. Dive deep and learn the shape of the concept, then write about it in your own words, then move on.<p>By writing from your own perspective it has 2 effects: 1) it helps solidify the concepts a bit more, because you can only explain something once you've reached a certain level of comprehension. and 2) it serves as a "stack snapshot" of your mind when you had a handle on the concept, and re-reading that snapshot loads the context back into your mind very quickly.
<p><pre><code> var a = new Array('5');
// what is a?
var a = 5 + '5';
// what is a?
</code></pre>
It's sad that many languages force people to memorize trivial stuff like this.<p>This is one of the things that really impressed me about Smalltalk/Pharo syntax when I started learning it recently. The language itself encourages you to name things in a way that labels all the parameters. E.g. you can have a constructor like this:<p><pre><code> OrderedCollection ofSize: 5.
</code></pre>
And method names are composed of parameter names:<p><pre><code> array insert: 11 before: 2.
</code></pre>
Instead of<p><pre><code> array.insertBefore(11, 12);</code></pre>
Similar to using spaced repetition to learn programming languages, you can use the same technique to organize your problem-solving skills sharpening sessions.<p>A while back I made a Chrome extension for LeetCode. [0] It takes care of scheduling problems for you and the extension users love it :) It costs only two dollars, so you might want to try it :)<p>[0]: <a href="https://spacedleet.imedadel.me/" rel="nofollow">https://spacedleet.imedadel.me/</a>
If anyone's interested - I've written a guide to Anki and spaced repetition. I've used it for about 5-6 years and my deck is about 12,000+ cards. Much of it is based in software engineering.<p><a href="https://senrigan.io/blog/everything-i-know-strategies-tips-and-tricks-for-spaced-repetition-anki/" rel="nofollow">https://senrigan.io/blog/everything-i-know-strategies-tips-a...</a>
If you're memorizing very specific information that's going to be presented to you in exactly the way you've memorized it, this is great. I am a little skeptical, however, about how well the specific information you've memorized generalizes to knowledge of the principles behind what you've memorized.<p>Taking one example from the article, if the front of the flashcard is:<p><pre><code> var a = 5 + '5';
// what is a?
</code></pre>
And the back is:<p><pre><code> '55'
If either side of + is a string, the other is
converted to a string before adding like strings.
</code></pre>
I'm sure it would work great if in a real programming context you're ever presented with literally: 5 + '5'<p>But whether you'll remember the principle that <i>"If either side of + is a string, the other is converted to a string before adding like strings"</i> when you see, say 237 + "foo" is open to question.<p>Of course, in this highly simplistic case you probably would remember, as it's not difficult to memorize this principle even without the flashcards, but with more complicated examples I suspect it could be a real problem.
Great post! Whenever I’ve gone down the path of trying to memorize stuff using spaced repetition or flash cards, it has rarely paid off. I’ve found that real practice works better for me. For example, I’ll create and run a vim macro command 10 times when I realize I’ve forgotten how to write macros. It’s like playing a musical instrument.
I just started a new job and have been learning Spark + Scala with Anki. Whenever I need to Google something, I make sure to make a flash card for it.<p>Its working well so far.
While Anki is great, I don’t see much value in using it for programming. I personally use it for equations and find it works very well. While remembering an equation is super useful, remembering APIs and stuff just isn’t. Intellisense solves the problem and even if you don’t have access to it (Python cough cough), it’s not that big a deal to just look up the documentation. Looking up the “documentation” (hah!) for equations is actually genuinely time consuming.