3 ms·
My suggestion is even if you cover multiple topics, do it one at a time. Do tmux, then notebooks, then whatever, instead of splicing one in to the other. Mixi
by SomeStupidPoint 10y ago
My suggestion is even if you cover multiple topics, do it one at a time.
Do tmux, then notebooks, then whatever, instead of splicing one in to the other.
Mixing topics just makes the material less effective at both things and hard to follow.
- jph00 10y agoYou may well be right, and that's certainly how material is usually taught. However my reading of the literature on this topic has led me to believe that the standard treatment is not the best approach for most students. I'm particularly influenced by David Perkins on this point - although I'm sure I could be applying his theories a lot better! My collaborator, Rachel Thomas, has written about these ideas : http://www.fast.ai/2016/10/08/teaching-philosophy/ http://www.fast.ai/2016/10/08/teaching-philosophy/ . We're learning as we go and we're spending a lot of time talking to our students to understand what's working and what's not. I hope each lesson sees some improvements...
- SomeStupidPoint 10y agoI think you misunderstood my point: It's okay to teach a little tmux, a little notebooks, and a little AWS each lesson, rather than the course be topic by topic. I agree with your point that it's a better way to teach material in a course, because it allows you to get people started doing things. My point was that within a lesson, you should separate topics, because people don't handle the topic switches well when trying to listen -- it's basically just a cache/stack smash. Diversions are distracting, even when materials are interwoven in the course.