Post-course evaluation notes
- Jeroen Laros
- Michiel van Galen
- Wai Yi Leung
- Martijn Vermaat
We want to involve the students more and push them to really do exercises. Afternoons off don't really seem to work for that. Instead, perhaps do 3 full days with some time for supervised exercises.
We have to very careful that it will not get boring for fast students when we wait for the slow ones.
Separate presenting from practice
Idea is to have more structure here. Ideally have good course material in written narrative, including exercises, which will be the backbone of the course. We introduce concepts in our presentations with separate slides, but these are always based on (or can refer to) the written course material.
This course material can be implemented in IPython notebooks, where the exercises have some empty code cells.
We also do just presentations, and separate this from some time for exercises afterwards. These can be intertwined as 20 or 30 minute sessions.
This lesson can be much sooner, e.g., after More Python Goodness.
Mode of operation
We introduce different modes of writing code:
- (I)Python interpreter
- IPython Notebook
- Text editor
This makes things more complex. Perhaps we can completely skip the first one?