3 ms·

At least for me this often means, that I just keep on lookin up the stuff over and over again. Takes some deliberate effort to actually store some obscure thing

At least for me this often means, that I just keep on lookin up the stuff over and over again. Takes some deliberate effort to actually store some obscure things in my memory. When I was still active with Anki, I was mostly picking up some random things I knew I would need fairly often and included those in my deck.

OJFord 3y ago
But that means you're doing tar flag flashcards more often than you're using those tar flags? Because otherwise, and for me, the CLI usage is the flashcard? Using them is what teaches me and keeps fresh the commands and flags that I most often use.
- Version467 3y ago
  Not necessarily. Hypothetical example, but let's say I use some obscure tar command twice a month. That's too far apart for me to remember it, but often enough that it would annoy me to look it up every time. Chuck it into anki and I have a short time where I repeat it often enough so that it sticks and after that the time between repetitions quickly becomes far longer than the 14 day interval where I actually use the command. And now I never have to look it up again :)
  - Arisaka1 3y ago
    I think that's the original claim: That you're memorizing something that you use 12-20 times per year. Why not turn that into a script, or make it a memorable alias?
    - Version467 3y ago
      Because I perceive the cost of memorizing it to be almost zero. There's of course a need for nuance here. I do write scripts to automate stuff and I do have aliases configured for certain commands, directories, etc. I don't try to remember all the things, just so that I never have to look something up again. If I wasn't a heavy anki user already, then I certainly wouldn't set it up just to remember some commandline stuff. But that's not the situation I'm in. I use it for lots of things already and I have an established habit to review the cards every day. Adding a card to remember specific flags has incredibly low overhead for me. A different, but similar example is using Anki for learning library/framework syntax. I made heavy use of it when I first learned Pytorch. There are so many different commands to wrangle your data into the shape you need it to be. I frequently mixed them up and got frustrated because it doesn't necessarily result in runtime errors and then it's hard to debug (because I didn't know what I was doing). So everyday I chucked a couple of the new commands I encountered into Anki and by the end of the week I was comfortable doing all kinds transformations. Would I have learned to do that without Anki? Probably. Did it give me an additional opportunity to consolidate that knowledge for very little cost? Also yes.
- ants_everywhere 3y ago
  This is the issue I've found with SRS style memorization in general. It's basically the definition of overfitting.

OJFord 3y ago

But that means you're doing tar flag flashcards more often than you're using those tar flags? Because otherwise, and for me, the CLI usage is the flashcard? Using them is what teaches me and keeps fresh the commands and flags that I most often use.

Version467 3y ago
Not necessarily. Hypothetical example, but let's say I use some obscure tar command twice a month. That's too far apart for me to remember it, but often enough that it would annoy me to look it up every time. Chuck it into anki and I have a short time where I repeat it often enough so that it sticks and after that the time between repetitions quickly becomes far longer than the 14 day interval where I actually use the command. And now I never have to look it up again :)
- Arisaka1 3y ago
  I think that's the original claim: That you're memorizing something that you use 12-20 times per year. Why not turn that into a script, or make it a memorable alias?
  - Version467 3y ago
    Because I perceive the cost of memorizing it to be almost zero. There's of course a need for nuance here. I do write scripts to automate stuff and I do have aliases configured for certain commands, directories, etc. I don't try to remember all the things, just so that I never have to look something up again. If I wasn't a heavy anki user already, then I certainly wouldn't set it up just to remember some commandline stuff. But that's not the situation I'm in. I use it for lots of things already and I have an established habit to review the cards every day. Adding a card to remember specific flags has incredibly low overhead for me. A different, but similar example is using Anki for learning library/framework syntax. I made heavy use of it when I first learned Pytorch. There are so many different commands to wrangle your data into the shape you need it to be. I frequently mixed them up and got frustrated because it doesn't necessarily result in runtime errors and then it's hard to debug (because I didn't know what I was doing). So everyday I chucked a couple of the new commands I encountered into Anki and by the end of the week I was comfortable doing all kinds transformations. Would I have learned to do that without Anki? Probably. Did it give me an additional opportunity to consolidate that knowledge for very little cost? Also yes.
ants_everywhere 3y ago
This is the issue I've found with SRS style memorization in general. It's basically the definition of overfitting.