Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design. By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement. Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.

1. Past Retreats:
1) 15th November 2014, GDCR, IDeaS, Pune.
2) 14th December 2013, GDCR, Equal Experts, Pune.
3) 8th December 2012, GDCR, MPSTME, Mumbai.
4) 6th October 2012, Equal Experts, Pune.
5) 4th August 2012, ASCI, BNP Paribas, Mumbai.
CodeRetreat
Ford Motor Company, Chennai.
14th August 2015.
Dhaval Dalal
@softwareartisan

2. Getting The Most
• Shrink the gap.
• Ideate and realise your experiments.
• Get out of your comfort zone.
• Pair with strangers in languages you don’t
know.
• Keep and open mind and make sure you
learn.
• Learn to detach yourself from your own
creation.

3. 4 rules of simple design
http://c2.com/cgi/wiki?XpSimplicityRules

4. Snakes And Ladders
• a game is over when any player reaches final cell first.
• a player can arrive at a new position by adding the
number to existing position from the throw of dice
• a player can arrive at final cell only by throwing on dice
the exact number of positions required to reach it.
• a player is promoted to head position of ladder when
they arrive at a cell containing ladder’s tail
• a player is demoted to tail position of snake when they
arrive at a cell containing snake’s head
• players take turns occupying new positions until the
game is over

5. Watch Lines/Files, Please
• <= 5 Lines Per Method.
• One/Two Level of Indentation Per Method.
• <= 25 Lines Per Class.

6. No Getters/Setters & no
more than one dot per
line
• Any form Getters or Setters or Properties not
allowed.
• One dot per line

7. No Conditions, Please
• Don’t use the else keyword.
• Don’t use the switch-case.
• Strive for not using ‘if’ if possible

8. Closing Retro
• What, if anything, did you learn today?
• What, if anything, surprised you today?
• What, if anything, will you do differently in
future?

9. Thank-you!