![]() ![]() This list has the special property where each province in the list is associated with one and only one country (i.e. Suppose you want to memorize the Provinces in Canada. Ī 1-n relationship is best understood by example. For example, your list can take a special form of a “1-n relationship”, as discussed in this thread. Sometimes you can take advantage of the inherent structure of a list to break the flashcard down. Aim for each sub-category to have 1-2 items. You can also lists into sub-categories and then add those smaller lists to spaced repetition. It will probably also increase the likelihood of being able to recall the entire list at once (even though it’s unlikely I’ll need to do that). Doing this will give a deeper understanding of the advantages of computers over humans. For example, I could add specific questions on the relative costs of computing compared to manual effort, or details about the speed of computing compared to hand calculations. Instead, I would look in the source to Ankify material focused on each individual point. So, I would not Ankify this specific list at all. For example, when I’m working on a process at work that is repetitive, rote, and requires accuracy, I want to recognize computer scripts as a good solution. Then ask yourself, what do I really want to get out of this list? In my example, I want advantages of computers over humans to pop up in my mind when the time is right. So, what are our options for dealing with these annoying lists? Break it Downįirst, ask yourself: do I really need to memorize the list? Do you really need to be able to spout off the list of advantages of computers over humans, and not miss any of points? Probably not. How do you rate your performance when you get 9 out of the 10 answers in the list correct? Do you fail yourself if you only got one wrong? A large number of simple cards is far more efficient to remember than a small number of big, demanding, awkward cards. The “Minimum Information Principle” states that your questions and answers should be as simple as possible. It violates a fundamental rule of flashcard creation.So, when it comes time to review, you’re not quite sure what’s on the list, and you may list things that are “correct” but just not included on that particular list. Also, many lists (including the example above), are open ended and not necessarily exhaustive. Even if you do individual cloze deletions for each point, you will still be very likely to fail on the question where you are asked to recall the entire list. It’s a lot to read, and you have to read every option to know what the missing one is.While this makes the cards easy to create, you’ll run into these issues when reviewing them: One easy approach is to cloze delete each individual option, and then cloze delete the entire list to make sure you can recall the whole thing. This is a frustrating passage, because it’s packed with valuable information but tough to turn it into flashcards. “People are sure the machine can never compete, ignoring all the advantages the machines have…These are: economics, speed, accuracy, reliability, rapidity of control, freedom from boredom, bandwidth in and out, ease of retraining, hostile environments, and personnel problems.” In the spaced repetition community, these are sometimes called “Sets” (see Anki Essentials, Chapter 7, “The 20 Rules”).įor example, here’s a section from a book I’m working through called The Art of Doing Science and Engineering by Richard Hamming, where he summarizes the main advantages of computers over humans: When adding cards to Anki (or any other spaced repetition system), you’ll find you often need to deal with lists. Photo by Glenn Carstens-Peters on Unsplash What are your “Big Projects”? December 30, 2022.Notes on “Why Take Notes” by Mark Nagelberg – Mark Nagelberg on Why Take Notes?.JoshuaPhynC on Notes on The Kimball Group Reader Chapter 1: The Reader at a Glance."Move" Python Script Into Airflow Running On Docker (Windows) - Programming Questions And Solutions Blog on Getting Started with Airflow Using Docker.What are your “Big Projects”? – Mark Nagelberg on The Hidden Power of Compounding (and 4 Ideas for Harnessing it).baccaratsite on Notes on The Kimball Group Reader Chapter 1: The Reader at a Glance.Notes on “3 Things I Wish I did as a Junior Dev” by Theo Browne.Notes on “Why Take Notes” by Mark Nagelberg.Notes on The Kimball Group Reader Chapter 1: The Reader at a Glance. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |