= 27d567bc2d48d9f40e9ccc20ea370b15)
JacekLach comments on 2013 Survey Results - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (558)
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.