際際滷

際際滷Share a Scribd company logo
CodeRetreat
Wix.engineering
Vaidas Pilkauskas (@liucijus)
Ittai Zeidman (@ittaiz)
History
Codemash conference 2009
Gary Bernhardt
Patrick welsh
Nayan Hajratwala
Corey Haynes
Coderetreat is a day-long, intensive practice
event, focusing on the fundamentals of software
development and design.
Coderetreat is our chance to practice outside of
work constraints.
Day format
 Intro (15 min) - We are doing it now
 3 sessions
 Nice long lunch
 2 sessions
 If you have enough energy - one additional session
 Closing circle
Delete your code!
For each session
 Find a new pair partner! Avoid pairing with colleagues you
work daily
 It is advisable to try other languages. But one in the pair
should be experienced with chosen language
 Do not try to finish the problem
 Focus on practicing
Four Rules of Simple Design / TDD cycle
 Passes the tests
 No duplication
 Reveals intention
 Fewest elements
 Write a failing test (make it red)
 Write minimal amount of code to pass
it (make it green)
 Refactor - improve design without
changing functionality
Game of Life
1. Any live cell with fewer than two live neighbours dies, as if caused by under-
population.
2. Any live cell with two or three live neighbours lives on to the next generation.
3. Any live cell with more than three live neighbours dies, as if by over-
population.
4. Any dead cell with exactly three live neighbours becomes a live cell, as if by
reproduction.
We are here to have fun - be awesome
to each other
Closing Circle
What, if anything, did you learn today?
What, if anything, surprised you today?
What, if anything, will you do differently in the future?

More Related Content

Coderetreat introduction

  • 2. History Codemash conference 2009 Gary Bernhardt Patrick welsh Nayan Hajratwala Corey Haynes
  • 3. Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
  • 4. Coderetreat is our chance to practice outside of work constraints.
  • 5. Day format Intro (15 min) - We are doing it now 3 sessions Nice long lunch 2 sessions If you have enough energy - one additional session Closing circle
  • 7. For each session Find a new pair partner! Avoid pairing with colleagues you work daily It is advisable to try other languages. But one in the pair should be experienced with chosen language Do not try to finish the problem Focus on practicing
  • 8. Four Rules of Simple Design / TDD cycle Passes the tests No duplication Reveals intention Fewest elements Write a failing test (make it red) Write minimal amount of code to pass it (make it green) Refactor - improve design without changing functionality
  • 9. Game of Life 1. Any live cell with fewer than two live neighbours dies, as if caused by under- population. 2. Any live cell with two or three live neighbours lives on to the next generation. 3. Any live cell with more than three live neighbours dies, as if by over- population. 4. Any dead cell with exactly three live neighbours becomes a live cell, as if by reproduction.
  • 10. We are here to have fun - be awesome to each other
  • 11. Closing Circle What, if anything, did you learn today? What, if anything, surprised you today? What, if anything, will you do differently in the future?