I don’t know what you work on, but many fields include bodies of loosely connected facts that you could in principle look up, but which you’d be much more efficient if you just memorized. In programming this might mean functions in a particular library that you’re working with (the C++ STL, for example). In chemistry, it might be organic reactions. The signs of medical conditions might be another example, or identities related to a particular branch of mathematics.
SRS would be well suited to maintaining any of these bodies of knowledge.
In programming this might mean functions in a particular library that you’re working with (the C++ STL, for example)
Right. I guess I somewhat do ‘spaced repetition’ here, just by the fact that every time I interact with a particular library I’m reminded of its function. But that is incidental—I don’t really care about remembering libraries that I don’t use, and those that I use regularly I don’t need SR to maintain.
I suppose medical conditions looks more plausible as a use case—you really need to remember a large set of facts, any of which is actually used very rarely. But that still doesn’t seem useful to me personally—I can think of no dataset that’d be worth the effort.
I guess I should just assume I’m an outlier there, and simply keep SR in mind in case I ever find myself needing it.
I’ve used SRS to learn programming theory that I otherwise had trouble keeping straight in my head. I’ve made cards for design patterns, levels of database normalization, fiddly elements of C++ referencing syntax, etc.
They’re mostly copy-and-pasted descriptions from wikipedia, tweaked with added info from Design Patterns. I’m not sure they’d be very useful to other people. I used them to help prepare for an interview, so when I was doing my cards I’d describe them out loud, then check the description, then pop open the book to clarify anything I wasn’t sure on.
edit: And I’d do the reverse, naming the pattern based on the description.
I don’t know what you work on, but many fields include bodies of loosely connected facts that you could in principle look up, but which you’d be much more efficient if you just memorized. In programming this might mean functions in a particular library that you’re working with (the C++ STL, for example). In chemistry, it might be organic reactions. The signs of medical conditions might be another example, or identities related to a particular branch of mathematics.
SRS would be well suited to maintaining any of these bodies of knowledge.
I’m a software dev.
Right. I guess I somewhat do ‘spaced repetition’ here, just by the fact that every time I interact with a particular library I’m reminded of its function. But that is incidental—I don’t really care about remembering libraries that I don’t use, and those that I use regularly I don’t need SR to maintain.
I suppose medical conditions looks more plausible as a use case—you really need to remember a large set of facts, any of which is actually used very rarely. But that still doesn’t seem useful to me personally—I can think of no dataset that’d be worth the effort.
I guess I should just assume I’m an outlier there, and simply keep SR in mind in case I ever find myself needing it.
I’ve used SRS to learn programming theory that I otherwise had trouble keeping straight in my head. I’ve made cards for design patterns, levels of database normalization, fiddly elements of C++ referencing syntax, etc.
Do you have your design pattern cards formatted in a way that are likely to be useful for other people?
They’re mostly copy-and-pasted descriptions from wikipedia, tweaked with added info from Design Patterns. I’m not sure they’d be very useful to other people. I used them to help prepare for an interview, so when I was doing my cards I’d describe them out loud, then check the description, then pop open the book to clarify anything I wasn’t sure on.
edit: And I’d do the reverse, naming the pattern based on the description.