Notes on Session 1

• go straight into the interaction, rather than the historical introduction?
• make sure bottom of Terminal is readable
• at least one person installed all their tools to the local network drive on campus! We need to make sure we’re being explicit about installing to the laptop in the instructions.
• typo in 01-jupyter.ipynb
• when you have the text available on the secondary screen, no need to show it on the primary screen: focus on the interactive cells, there.
• asking people to guess what an answer is when it’s in the documentation in front of them seems weird
• would be better to have blank cells and get students to type, rather than just ctrl+enter all the time
• too slow through the early section (history, etymology) maybe, then too fast through new concepts like strings and lists
• the string, list, for loop and function sections really need a foundation-building exercise for students to internalise the conceptsn we refer to importance of practice, but don’t provide any
• more reminders of red/green stickies would be useful
• introduce one concept at a time - when introducing principles of functions, digressing on to docstrings (which we don’t teach) breaks flow
• string methods don’t get referred to again and could be dropped for time
• mentioning object-orientation is another digression; we’re trying to teach basic concepts
• could speed up through discussion of less to get through to the more useful bits
• reading each line from the document is slow; could skip most of this using the interactive sections as waypoints
• the speaker should point out red stickies to helpers, rather than go into the audience
• clear text search history if possible beforehand; avoids embarrassments ;)
• I was overzealous clearing one of the code cells; apologies (LP)
• digressions slow things down; too much on Artemis features?
• typo in 03-parsing “eurkaryotes”
• verbal discussion of CDS=True is potentially a digression; maybe mark up sections of text as ‘tips’ to skip during the lesson?