When setting up a new club, it might be helpful to answer some questions together, to help define and understand what each other's goals are and if there is an overall purpose for your club.
- More guidelines for facilitating
- Make it clear people should not be allowed to interrupt
- Should people be reading code before the session?
- Should comments be removed from code? No we even found interesting that some were inaccurate (that was news to beginners). We want the code to be real.
- Should parts of the code be removed if judged 'unimportant' to shorted the file? No, that makes identifying the important lines biased / or easier. We want to see real whole code.
- Quality of the code is important
- Diversity of languages is interesting, but if same language is used, we can go deeper each session
- Look at the same task in the same language, done in different ways
- Look at the same task done using different languages
- Study the same code over 2 sessions
- Study the same code in 2 groups and then come together to discuss. Segment by programming experience
- Guidelines for selecting code to read
- Study deliberate sets of code for progression
When setting up a new club, it might be helpful to answer some questions together, to help define and understand what each other's goals are and if there is an overall purpose for your club.