30

Agileday Coderetreat 2013

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Agileday Coderetreat 2013
Page 2: Agileday Coderetreat 2013

+ SPONSOR =• COMPANIES &• PEOPLE

Page 3: Agileday Coderetreat 2013
Page 4: Agileday Coderetreat 2013
Page 5: Agileday Coderetreat 2013

CODERetreat

Page 6: Agileday Coderetreat 2013

•CHALLENGE•REPEAT•FEEDBACK

DELIBERATEDEEP

PRACTICE

Page 7: Agileday Coderetreat 2013
Page 8: Agileday Coderetreat 2013

NO PRESSURE

feel free toexperiment

Page 9: Agileday Coderetreat 2013

NO PRESSUREdo not complete thetask but master it

Page 10: Agileday Coderetreat 2013

FORMAT of the DAYfrom 10:00 to13:00

MORNING

from 13:00 to14:00

LUNCH

from 14:00 to17:00

AFTERNOON

Page 11: Agileday Coderetreat 2013

45 min coding

10 min retrospective

5 min break

FORMAT of the DAY

Page 12: Agileday Coderetreat 2013

CODING

Page 13: Agileday Coderetreat 2013

1. PASSES ALL ITS TESTS2. CLEARLY EXPRESSES INTENT3. CONTAINS NO DUPLICATION4. HAS NO SUPERFLUOUS PARTS

SIMPLE DESIGN

Page 14: Agileday Coderetreat 2013
Page 15: Agileday Coderetreat 2013
Page 16: Agileday Coderetreat 2013

DELETEYOUR CODEAFTER EACHSESSION

Page 17: Agileday Coderetreat 2013

PAIR

AFTER EACH SESSION

Page 18: Agileday Coderetreat 2013

WE LOVETO SEEMULTIPLEPROGRAMMINGLANGUAGES

Page 19: Agileday Coderetreat 2013

VARIATIONS• AVOID TO USE PRIMITIVES• AVOID TO USE ELSE IN CONDITIONS• EXTREME TELL DO NOT ASK• MAX OF 5 LINES OF CODE PER METHOD• PING PONG PROGRAMMING• TRY TO USE DIFFERENT CONCEPTS

(GRID GAME CELL...) AS A CENTER

Page 20: Agileday Coderetreat 2013

VARIATIONS• AVOID TO USE CONDITIONS• TRY TO GUESS THE RESULT OF TESTS• DO NOT USE ARRAYS• USE ONLY INTERACTION BASED TESTS• USE ONLY STATE BASED TESTS• ALL METHODS RETURNS VOID

Page 21: Agileday Coderetreat 2013

VARIATIONS• DO NOT TALK WITH YOUR PAIR• TDD AS IF YOU MEANT IT• DO NOT USE THE MOUSE• ONLY USE AUTOMATIC REFACTORINGS• OCP STYLE

Page 22: Agileday Coderetreat 2013
Page 23: Agileday Coderetreat 2013

THE GAME OF LIFE IS A TWO

DIMENSIONAL GRID OF SQUARE CELLS

EACH OF WHICH IS IN ONE OF TWO

POSSIBLE STATES ALIVE OR DEAD

Page 24: Agileday Coderetreat 2013

AT EACH STEP IN TIME EVERY CELL INTERACTS WITH ITS 8 NEIGHBORS

FOLLOWING 3 RULES

Page 25: Agileday Coderetreat 2013

1. ANY LIVE CELL WITH FEWER THAN 2 LIVE NEIGHBORS DIES OF LONELINESS

Page 26: Agileday Coderetreat 2013

2. ANY LIVE CELL WITH MORE THAN 3 LIVE NEIGHBORS DIES OF OVERCROWDING

Page 27: Agileday Coderetreat 2013

3. ANY DEAD CELL WITH EXACTLY 3 LIVE NEIGHBORS COMES TO LIFE OF WARMTH

Page 28: Agileday Coderetreat 2013

LIFE EVOLUTION1 2 3

Page 29: Agileday Coderetreat 2013

LIFE EVOLUTION1 2 3

Page 30: Agileday Coderetreat 2013

LIFE EVOLUTION1 2 3