Open badlydrawnrob opened 5 years ago
Using the simple card, a basic example:
If the question isn't short and sweet, it may be too complicated ... but, potential issues with current fields are:
Any ideas or examples, please send them along!
Look up more information on Image Occlusions plugin and this post which goes into detail on building your own ...
Some ideas are too complex for a simple flashcard. For example, the HTDP game code or a stonking great glob of code from a program. How can this be broken down to make reviews sane? Should only a handful of snippets from the code base be added?
23 (see the game, also the notes table)
72 (especially on when NOT to add cards)
concrete->pictorial->abstract
approach to teachingInitial thoughts on sketching out ideas
When writing a function or programme, there'll be many routes. Each will have it's pros and cons, some will lead to shorter (or easier) code — having visuals of design decisions could come in handy when reviewing cards.
See also hammock driven development for thinking about a problem, and ideally a non-maths version of "How to Solve it" if one exists. Some problems will need context, or step-by-step drawings, but where possible get to the nugget of the issue without adding a ton of code (this could be handled with simple drawings or explanations).
See the below comment, and my Head First SQL book notes as an example of where Anki might not be necessary. Here I've pulled out key ideas in a document for reference, and it only makes sense to add an Anki card on bits you routinely get stuck on.
If you come back to your notes and a section is too hard to understand, it's probably a good candidate for a simpler Anki card.
Image occlusions in Anki
Image Occlusions are another area to explore. The only downside is you must add annotations via Anki to validate the card. An example here on building your own.
Some things are hard to visualise
racket
lang.Some concepts are really hard (or really dry) to grasp, so it's sometimes easier to draw out in a conceptual, abstract way.
Programming terminology can be dense
Programming deals with precision for commanding a computer, so they can be hard to understand for the beginner. There's also the question of depth of understanding — and how to explain a thing depending on that student's knowledge reference points. A great example of this is Richard Feinman's explanation of magnets, and why they repel.
Some languages are easier to understand than others. It would be helpful to have a glossary for all the jargon out there!
Some other helpful examples