Feedback thoughts from participants #315
Description
- more functions/efficient programming - can point to resources
- data for projects ahead of time - which we did (so need to make this more obvious but idk if we had data tab before) hopefully just need to explain more times
- more community/getting to know each other and collaboration - more slack activities?
- make it more clear how to change labs - could explain this more times /emphasize
- more structure to project or have people prepare questions and data ahead of time - could explain this more times and ask for people's plans ahead of time
- can't read black bar on website -different color?
- want materials ahead of time - maybe not a good idea? but could give more practice for beforehand?
- want more homework
- two hw 2 files? (name hw by topic in addition to allow differentiation) - will check this
- ice breaker activities or something else to encourage people taking breaks at code-a-thon
- smaller specific stand ups if you know what projects are ahead of time
- want feedback after lightning talks - we would need to curate but could do this
- some didn't understand point of lightning talks - could describe this!
- review at code-a-thon - could do some of this but will take time - maybe a brief one if people want it - could basically go through cheatsheets?
- give schedule in advance for overall days (I thought we did this when they signed up?)
- | more modeling -could point to resources
- | how to read documentation - could make something about this