2 ms·
Having enough command of background facts to quickly figure things out is useful, but beyond that, knowing where to look up the facts seems like a perfectly fin
by _delirium 16y ago
Having enough command of background facts to quickly figure things out is useful, but beyond that, knowing where to look up the facts seems like a perfectly fine substitute for memorizing them. The real problem is if you know so little that you don't even know how to figure out what you need.
- pohl 16y agoknowing where to look up the facts seems like a perfectly fine substitute for memorizing them I suspect that you might revise this statement if you applied the simple metacognitive strategy of thinking about this as if you were a software system: if you put all of your facts on the other side of a high-latency lookup system — as you are suggesting — you limit the size your brain's base of associative firings. The work that one does to bring facts into the brain instead of leaving them in external storage allows those concepts to be quickly brought into the short-term "working memory" system where they can take part in cognitive activities. Eschewing practice and memorization limits the rate and scope of your thoughts. Worse yet, you won't know what you're missing. (This is the basic reason that Paul Graham's Blub programmer doesn't know what he's missing.)
- deleted 16y ago[deleted]
- tomjen3 16y agoI used to think that too - and to some extend, it is certainly true - but the problem is that you can't really derive new things without knowing old things, and you simply can't make mental connections between things unless you know them.
- _delirium 16y agoI agree there are large classes of things like that, but I think there are also large classes of things where looking them up is fine--- and my guess, though I could be wrong, is that the things traditionally memorized in schools lean more towards the second. If you think of the kinds of information that comes in tables, I think it's important to know that the table exists, and what kind of information is in it, when you would want to consult it, and ideally even how you would recreate it if you needed to. But actually memorizing the table? Doesn't seem that useful, and I think that's the kind of thing traditional tests have focused on (say, memorizing a bunch of different combinatorial identities, or memorizing a bunch of properties of chemical elements). That's especially the case when nobody in the real world would be in some bizarre situation where they're stuck on a desert island having to do things entirely from memory. For example, if you're doing big-O analysis of an algorithm, it's perfectly reasonable to assume that you'll have Maple or Mathematica, or at least a list of common identities, available to use when simplifying your result or solving recurrences.