Successfully reported this slideshow.
Your SlideShare is downloading. ×

Code Retreat Vsetin 12/08/2012

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Upcoming SlideShare
Como agregar un linc
Como agregar un linc
Loading in …3
×

Check these out next

1 of 19 Ad

More Related Content

Similar to Code Retreat Vsetin 12/08/2012 (20)

Advertisement

Code Retreat Vsetin 12/08/2012

  1. 1. Global Day of Code Retreat Vsetin 12/08/2012
  2. 2. Global Day of Code Retreat 12/08/2012 • 100 Locations • Czech Republic: Prague, Vsetin
  3. 3. Code Retreat • Pair Programming • Different Languages, Different Activities • Test Driven Development • Comfort Zone Breaking • Skills Improvements • Design Principles • Quality Constraints Activities • Socializing
  4. 4. Pair Programming
  5. 5. Schedule • 8.00 - 8.45am : arrival, coffee/breakfast • 8.45 - 9.00am : welcome, introductions, explanation of the problem • 9.00 - 9.45am : Session #1 • 9.45 - 10.00 am : retrospective, break • 10.00 - 10.45am : Session #2 • 10.45 - 11.00 am : retrospective, break • 11.00 - 11.45am : Session #3 • 11.45 - 12.00 pm : retrospective, break • 12.00 - 1.30pm : lunch, socializing • 1.30 - 2.15pm : Session #4 • 2.15 - 2.30pm : retrospective, break • 2.30 - 3.15pm : Session #5 • 3.15 - 3.30pm : retrospective, break • 3.30 - 4.15pm : Session #6 • 4.15 - 4.30pm : retrospective, break • 4.30 - 5.00 pm : Closing circle
  6. 6. Game of Life - Rules 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 overcrowding. 4. Any dead cell with exactly three live neighbours becomes a live cell, as if by reproduction.
  7. 7. Game of Life - Examples
  8. 8. Session #1 9.00-9.45am • Game of Life Basics • Navigator - Driver
  9. 9. Rules of Simple Design 1. Runs all the tests 2. Contains no duplications 3. Expresses the intent of the programmers 4. Minimizes the number of classes and methods
  10. 10. Rules of Test Driven Development 1. You are not allowed to write any production code unless it is to make a failing unit test pass. 2. You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures. 3. You are not allowed to write any more production code than is sufficient to pass the one failing unit test.
  11. 11. Session #2 10.00-10.45am • Simple Design • English • Baby Steps
  12. 12. Session #3 11.00-11.45am • Paper Only (10 min) • No Mouse
  13. 13. Launch 12.00-1.30pm
  14. 14. Session #4 1.30-2.15pm • Ping Pong • Mute
  15. 15. Session #5 2.30-3.15pm • Only 4 Lines per Method • No Conditional Statements • No Naked Primitives
  16. 16. Session #6 3.30-4.15pm • Changing Requirements – Configurable Rules – Cell Age
  17. 17. 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?
  18. 18. Gold Sponsor www.magion.cz
  19. 19. Afterparty

×