Some Suggestions for Teaching Python
curiousefficiency.org
curiousefficiency.org
Teaching using the interactive REPL might possibly be an anti-pattern when it comes to teaching a language. I mean, it's great to introduce, but walking through concepts with it can be quite painful:
1. When you get into unclosed brackets and quotation marks, beginners are often confused why nothing happens even after pressing "Enter" a few times. Yes, the prompt does signal an unclosed entity, but it's not obvious to beginners.
2. When you're demonstrating via projected display...it is very hard for students to determine exactly what the hell you're typing, especially if you take advantage of history-autocomplete shortcuts. Yes, such a thing is so mind-numbingly obvious to a moderately experienced programmer, but it is not at all the case for newbies.
3. If you're writing a sequence of commands...not only do you not have to make a typo, but so do your students. Try diagnosing a cry of "It didn't work!" when there are 3 to 4 lines that could have any variety of typographical error.
I think getting into the REPL to do "hello world" is fine...and it's probably necessary to show some basics about variables...but afterwards, it seems much more efficient to get into writing script files and executing them via command line than it is to continue using the REPL.
In fact, just did a back-of-the-envelope calculation. In an extremely conservative estimate, I have spent more than 30,000 hours working face-to-face with students teaching them how to code.
Actually I guess this explains why everyone sucks at teaching coding: nobody has enough experience.