- Set aside an hour and a half for this club.
- Your subsequent sessions can be shorter, but it's good to leave enough time to go through things in more detail when you first start.
- It's important to leave enough time for everyone to get involved and have an understanding.
- The facilitator should familiarise themselves with the session 1 agenda before the session, but everyone else just needs to turn up. It's helpful for everyone to be able to see the agenda during the session, so either send the participants a copy or share one online.
- It's best if the participants do not look at the code before the session, but they'll need to arrive with a copy (printed or digital) ready for marking up.
- It's best if the participants don't know anything about the code before the session starts.
- It's often fun to do a big reveal of where the code came from, if it relies on a framework and even sometimes, what language it is.
This session 1 code is written in Swift for the messaging app Signal and can be found: signalapp/Signal-iOS