2017 debrief
Ideas:
- To get more systematic feedback, solicit it during the course.
- Plan for a better wrap-up, select the most successful participants to present. Maybe also engage the participants by asking them to present at the end of each day.
- Review timing and contents of shell
- Piping has questionable usefulness within the course. Potentially make these an advanced exercise
- Maybe move tab and history earlier
- Consider making the advanced projects a single shared theme of the last days.
- Add exercises to follow during the lectures (with 15 minutes lectures followed by a short exercise)
- Consider adding advanced git topics:
- branches are a popular request
- we don't touch checkout, but we probably should (what about detached head?)
- .gitignore
- CI
- Code structure: add an exercise for refactoring; where to find such "dirty code"?
- Move OOP to the driver, make driver a refactoring exercise as well, guide people better through interaction with hardware.
- Invite people to come up in advance with a project topic from their own research (explain the context)
- Give more information to the course description and the signup form
Edited by Anton Akhmerov