Since we will try to video conf in multiple locations, probably into one hangout, it will be essential to be in the same timezone. The suggestion here is to sync via video only if you are in the same time zone, so you can really sync on the same thing at the same time.
5 Sessions x 45 minutes
|9:00||Arriving, Breakfast, Coffee|
|9:30||What is Code Retreat, what can u expect ... what is GameOfLife|
Explore the game of life, find out how it works.
Stabilize the rules so there are no questions left, analyze and practice to find out asking the right questions and answer them, sketch it on paper.
Implement a possible solution on paper. If you find out in this step that you don't know how to implement it go back to a step before and keep iterating until you have a solution. The implement step does also mean that you sketch out the test cases you have in mind and try to put them in an order that you find useful to achieve results along the lines of the given task.
Restriction: Mute Ping/Pong.
During the Pair Programming session nobody speaks. Person 1 writes a failing test, passes the keyboard to Person 2 who makes the test pass and writes another failing test, and then passes the keyboard back to Person 1, and so on. One test at a time.
Session 3 - Randori
Round robbin in teams of about 10 people. Use pair programming in the real sense, a driver and a navigator and take 3 minutes to implement the tests and production code. Move on to the next person to be navigator/dirver, so that the entire team is implementing at least once.
Session 4 - Pure functional
Use functional techniques to implement the game of live. Try not to use the `var` statement but just function. You have things available like map, forEach, filter, etc. Look up the array docs if you want to find out more.
Restriction: Extreme Baby Steps.
In this session we use small intervals of 2 minutes and go throw this procedure:
|17:00||Beers together ...|