Learning: grouping together of concepts

[badlydrawnrob]

Related concepts for learning

• But I'm a kid! I don't know that yet. anki#103
• Learning: Mush together some related concepts #3
• Learning: Did you understand the problem? #8 (comment)
• Draw! anki#50 (comment) ¹
• 3 times, 3 ways anki#93
• How to learn coding in the age of Artificial Intelligence? anki#92
• Learning: Mush together some related concepts #3 (comment)
• 👍 Learning: A better way to create cards? #10 (comment) (this is a very important idea²)

Methods of teaching

• Guide to teaching in the classroom (from kids up)
• Graph paper programming (and other examples some a bit babyish)
• Getting physical to learn coding — rock, paper, scissors
• Different ways to learn programming (Raspberry Pi white-paper)
• How about post-it notes and a whiteboard?
• Using Relia in the classroom

Footnotes

1. A black box procedure should be obvious to it's input and output, but the user does not have to know anything about the internal mechanism. You should be able to change the inner workings and keep the same inputs and outputs (or at least, refactor with minimal fuss) ↩

2. ... The footnote was all about drilling down to an Explain it like I'm 5 mindset, that assumes nothing. You can't use 'quote until you understand what (quote "this") means, and to begin with, it's probably best left out. Using the finger painting analogy, most (young) kids when given a bunch of paint don't think "which colours will match this colour?" — they smush all the colours together in a muddy mush. Go from Turtle commands or simple shapes (which, by the way, is terrible documentation for beginners), to compound commands and don't expect them to know anything. ↩