Name: code-fair
Owner: Turing School of Software & Design
Description: Directions and materials for Turing student code fairs
Created: 2017-06-01 18:55:11.0
Updated: 2017-06-26 01:17:33.0
Pushed: 2017-07-21 15:40:49.0
Homepage:
null
Size: 3865
Language: null
GitHub Committers
User | Most Recent Commit | # Commits |
Other Committers
User | Email | Most Recent Commit | # Commits |
README
code-fair
Directions and materials for Turing student code fairs
Initial Form Data Cleanup
- [ ] Standardize module field (cohort number vs module number, B/FEE vs B/FE, etc.)
- [ ] Standardize names wrt groups & capitalization
- [ ] Shorten all project descriptions to a standard format (ie, “Project name or short description of functionality w/ associated languages/libraries“)
- [ ] If a Posse signed up as a single student, change the name to the name of the Posse
Recommendations for Organizing Presenters
- [ ] Colocate projects with the same presenter (ie, Posse members with personal projects)
- [ ] Group presenters by cohort (though this was up for debate in SAB, so maybe try a random assortment next time around and see which is preferable)
- [ ] Consider assigning group projects to larger tables