1. Passes tests.

2. Reveals intent.

3. No duplication.

4. Fewest elements.

4 rules of simple design

Learn how to write code that adheres to the rules of simple design in order to minimize the cost of change.

 “I didn’t have time to write a short letter,

  so I wrote a long one instead.”

        - Mark Twain

• Any live cell with fewer than two live neighbours dies, as if caused by underpopulation.
• Any live cell with more than three live neighbours dies, as if by overcrowding.
• Any live cell with two or three live neighbours lives on to the next generation.
• Any dead cell with exactly three live neighbours becomes a live cell.

At each step in time, the following transitions occurs

The initial pattern constitutes the seed of the system.

The first generation is created by applying the above rules simultaneously to every cell in the seed, births and deaths happen simultaneously, and the discrete moment at which this happens is sometimes called a tick (in other words, each generation is a pure function of the one before).

The rules continue to be applied repeatedly to create further generations.

9 - 9.45am                - welcome and explanation of the problem

10 - 12pm                 - sessions and retros

12 .45- 1.30pm        - lunch, socializing

1.30 - 4.30pm          - sessions and retros

4.30 - 5pm               - closing circle

Schedule

• After each session, pairs should be swapped
• After each session, code must be deleted, not put in a branch, not stashed, just deleted with no trace left

Structure