Feedback 2018
Feedback day 1
Suggestions
- Breaks
- coffee
- Split the course
- solutions
- More optional exercises
- announce the program
- group by skill
- preparation material
- references for more
bad
- lunch
- too slow/basic (8x)
- too much time for short exercises
- too much stuff in 1 day (3x)
good
- post-its
- everything good (≥10x)
- organization
- a lot of instructors/enthusiastic
- materials
- github app or whatever
Feedback day 2
Suggestions
- where can I find the permanent course material repository
- a rough course schedule would be nice to have
- it would be great to know in advance when you have how much time to explore problens to thing about what might be useful to program
- do lectures together
- can you also recommend if homebrew is a good package installer instead of pip/anaconda
- you might have gotton different search results @ the problem solving because you use a different pc... google searcg history&co (big brother is taking care of you)
- live programming can be a bit distractive
- encourage people to compare their solutions
- tell more about the pythonic way of programming and about code efficiency
- lunch still has room for improvement
- maybe include some easier smaller tasks for people struggling with the more compelx tasks some cleare exercises with plotting
- upload the course materials 1 day before
- cut the numpy lecture into parts with exercises for each part (rather than all exercises at once)
Bad
- 5 people said pace is too fast
- 3 people said the sessions are too overloadad
- exercise session was too long and exhausting
- examples were hard to understand
- 2 people said lectures too long; more time for exercises
Good
- 4 people liked exercises
- 8 (1 of which also liked the execises) people are happy in general
- 1 person was explicitely happy with the fact we are taking action on their comments
- 6 people are happy with the instructors
- 2 people happy with the problem solving lecture
- lunch
- thanks for providing solutions
- good tempo
- clear explanation of how to avoid writing inefficient code
Feedback day 3
Good
- Nice selection of projects
- good
- git (x8)
- instructors (x2)
- own time to try things out (x2)
Bad
- No systematic explanation
- Disconnected from shell
Suggestions
- More systematic git (x3)
- More time for small exercises
- Make slower demonstrations
- Only now usefulness of shell is clear
- Installation instructions
Feedback day 4
Good
- Amazing!
- Quick and good advice (2x)
- The project helps to motivate people (2x)
Bad
- No exercises for the structure part makes it hard
- Doing the projects requires knowledge that is not in the course
Suggestions
- More exercises
- More concrete tips to make the code more readable and structured (2x)
- Moning was a bit too abstract
- Would like to learn debugging