This event is in the past
Go to the upcoming JS CodeRetreat

JavaScript Code Retreat #1

The Schedule

JavaScript Code Retreat #1




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.

Five Sessions

5 Sessions x 45 minutes

8:30 Arriving, Breakfast, Coffee
9:15 Introduction round
9:30 What is Code Retreat, what can u expect ... what is GameOfLife
10:00 Session 1
Restriction: No conditions at all.

We start with not using any conditional statements (eg if/else). This restriction forces the partners to think about there design and to make sure that both know the challenge.
10:45 Local Retrospective
11:00 Global Retrospective
11:30 Session 2
Restriction: Mute Ping/Pong.

During the Pair Programming session nobody speaks. This is an effective method to force the participants to wirte clear and meaningfull function-names and to take care of the names of any variables
12:15 Local Retrospective
12:30 Global Retrospective
12:45 Lunch
13:30 Session 3
Restriction: Extreme Baby Steps.
In this session we use small intervals of 2 minutes and go throw this procedure:
  1. Write exactly one test
    1. If the timer rings and the test is red then revert and start over
    2. If the test is green before the timer rings then go to 4
  2. Restart the timer no discussions in between
  3. Refactor
    1. If the timer rings and the refactoring is not complete then revert and start over
    2. If the refactoring is complete before the timer rings then you´re fine and go to the next step ;-)
  4. Go to 1
14:15 Local Retrospective
14:30 Global Retrospective
15:00 Session 4
Randori (3 groups, projector each group).
We will do Pair Programming and TDD in 3 groups in Randori-Style. This means that the whole groups works on the kata, we´ll switch the pair at the keyboard according to the mechanism chosen (2 or 3min). The group is expected to follow what is going on and the pair at the keyboard should explain what they are doing so everyone can follow.
15:45 Local Retrospective
16:00 Global Retrospective
16:30 Session 5
Restriction: Some Object Calisthenics
  • don't use ELSE
  • at most one level of indentation per method
17:15 Local Retrospective
17:30 Global Retrospective
17:45 Beers together ...