Coderetreat @Sibiu 2012 08 18
0 likes278 views
A code retreat is a 1-day intensive coding session where participants pair program through different coding challenges and practice techniques like test-driven development. The day consists of multiple coding sessions with different constraints, each followed by a retrospective. Participants work through problems like Conway's Game of Life, taking baby steps to write tests and code incrementally, and brutally refactoring code. The goal is to learn through pairing, extend comfort zones, practice techniques like TDD, and have fun experimenting with different approaches to coding.
Coderetreat @Sibiu 2012 08 18
- 2. www.mozaicworks.com Me Adi Bolboaca Organizational & Technical Trainer & Coach
- 3. Why? Learn through pairing Extend your comfort zone Practice Experiment Learn new practices www.mozaicworks.com
- 4. How? 1 day of coding Choose a simple problem 6 pairing partners On average 135 minutes of coding 6 different constraints A lot of fun! www.mozaicworks.com
- 5. How it started CodeMash conference 2009 Gary Bernhardt Patrick Welsh Nayan Hajratwala Corey Haines www.mozaicworks.com
- 6. How it started Repeatable Day-long Practice the fundamentals of programming Intense day of coding www.mozaicworks.com
- 7. Day structure 15' introduction 3 sessions of 45' coding + 15' retro&break 1h lunch 3 sessions of 45' coding + 15' retro&break 15' closing circle www.mozaicworks.com
- 8. Principles Language agnostic Do not try to finish the problem Delete the code after each session Focus on practicing Experiment each session Have fun! www.mozaicworks.com
- 9. Prerequisites Computer Coding environment Testing framework Source control (git, svn, etc) www.mozaicworks.com
- 10. The four elements of simple design 1) Passes its tests 2) Minimizes duplication 3) Maximizes clarity 4) Has fewer elements www.mozaicworks.com
- 11. Conway's game of life Having an infinite 2D orthogonal universe Being given an initial generation called a seed The following rules are applied simultaneously A live cell having less than 2 live neighbors dies A live cell having 2 or 3 live neighbors lives A live cell having more than 3 neighbors dies A dead cell having 3 neighbors becomes alive www.mozaicworks.com
- 12. First session Find a pair Choose a programming language Setup the environment Choose an entry point for the problem Start in 5 min www.mozaicworks.com
- 13. Conway's game of life Having an infinite 2D orthogonal universe Being given an initial generation called a seed The following rules are applied simultaneously A live cell having less than 2 live neighbors dies A live cell having 2 or 3 live neighbors lives A live cell having more than 3 neighbors dies A dead cell having 3 neighbors becomes alive www.mozaicworks.com
- 14. Session constraints at your choice No conditionals (if, while, etc) No loops (for, foreach, while, etc) Four lines of code per method Use only one dot/arrow per line www.mozaicworks.com
- 15. Taking Baby Steps 1) Initialize source control repository 2) Start a timer for 2 minutes 3) Write exactly one test a) Timer rings, the test is red, then revert and go to 2) b) The test is green before the timer rings, then commit 4) Restart timer 5) Refactor a) Timer rings, the refactoring is not complete then revert and restart b) The refactoring is complete before the timer rings, commit and go to 2) Obs. The timers must run continuously, don't stop to talk! www.mozaicworks.com
- 16. Code retreat 1 hour Lunch www.mozaicworks.com
- 17. TDD as if you meant it 1) Write exactly one failing test 2) Make the test pass by writing implementation code in the test method 3) Create a new implementation method by: a) Extracting implementation code to a new method in the test class b) Moving implementation code into an existing implementation method from the test class 4) Create implementation classes to provide a destination for extracting a method in the test class 5) When necessary move implementation methods into implementation classes 6) Refactor as required www.mozaicworks.com
- 18. Brutal refactoring game www.mozaicworks.com 1)Lack of tests 2)Name not from domain 3)Name not expressing intent 4)Unnecessary if 5)Unnecessary else 6)Duplication of constant 7)Method does more than one thing 8)Primitive obsession 9)Feature envy 10)Method too long (> 6 lines) 11)Too many parameters (> 3) 12)Test – not unitary 13)Test – setup too complex 14)Test – unclear Act 15)Test - more than one assert 16)Test – no assert 17)Test – too many paths
- 19. Code retreat Choose your own practice Decide with your pair in the first 5 minutes www.mozaicworks.com
- 20. Closing circle 1) How did you feel? 2) What did you learn today? 3) What will you do differently on Monday? www.mozaicworks.com
- 21. Code retreat Why? Learn through pairing Extend your comfort zone Practice Experiment Learn new practices www.mozaicworks.com
- 22. Contact me ● Remote pair-programming ● Unit testing workshop ● Test driven development workshop ● Clean code workshop ● Refactoring workshop ● Legacy code retreat ● Legacy code workshop ● Code retreat www.mozaicworks.com
- 23. Code retreat Extend your mentoring & training capacity Accelerate learning through communities of practice Grow your functional leaders and top talents http://www.mozaicworks.com [email protected] @adibolb