global day of coderetreat @cluj-napoca 2012 12 08
DESCRIPTION
TRANSCRIPT
www.mozaicworks.com
Me
Adi BolboacaOrganizational & Technical
Trainer & Coach
Why?
Learn through pairingExtend your comfort zone
PracticeExperiment
Learn new practices
www.mozaicworks.com
How?
1 day of codingChoose a simple problem
6 pairing partnersOn average 135 minutes of coding
6 different constraintsA lot of fun!
www.mozaicworks.com
How it started
CodeMash conference 2009
Gary BernhardtPatrick Welsh
Nayan HajratwalaCorey Haines
www.mozaicworks.com
How it started
RepeatableDay-long
Practice the fundamentals of programmingIntense day of coding
www.mozaicworks.com
Day structure
15' introduction3 sessions of 45' coding + 15' retro&break
1h lunch3 sessions of 45' coding + 15' retro&break
15' closing circle
www.mozaicworks.com
Principles
Language agnosticDo not try to finish the problem
Delete the code after each sessionFocus on practicing
Experiment each sessionHave fun!
www.mozaicworks.com
Prerequisites
ComputerCoding environmentTesting framework
Source control (git, svn, etc)
www.mozaicworks.com
The four elements of simple design
1) Passes its tests2) Minimizes duplication
3) Maximizes clarity4) Has fewer elements
www.mozaicworks.com
Conway's game of life
Having an infinite 2D orthogonal universeBeing given an initial generation called a seedThe following rules are applied simultaneously
A live cell having less than 2 live neighbors diesA live cell having 2 or 3 live neighbors lives A live cell having more than 3 neighbors diesA dead cell having 3 neighbors becomes alive
www.mozaicworks.com
First session
Find a pairChoose a programming language
Setup the environmentChoose an entry point for the problem
Start in 5 min
www.mozaicworks.com
Conway's game of life
Having an infinite 2D orthogonal universeBeing given an initial generation called a seedThe following rules are applied simultaneously
A live cell having less than 2 live neighbors diesA live cell having 2 or 3 live neighbors lives A live cell having more than 3 neighbors diesA dead cell having 3 neighbors becomes alive
www.mozaicworks.com
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
Single Responsibility Principle
Name the methods to contain all their responsabilities
When the method name has “and” or “or” then split the method
No conditionals: ifs, switch, etcNo try/catch
Exactly one assert per testTest one behaviour per test
www.mozaicworks.com
Taking Baby Steps1) Initialize source control repository2) Start a timer for 2 minutes3) Write exactly one testa) 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 timer5) Refactora) 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
Pair-programming games
Ping-pong pair-programming at choice with:
Evil codingMute pairing
www.mozaicworks.com
Code retreat
Choose your own practice
Decide with your pair in the first 5 minutes
www.mozaicworks.com
Closing circle
1) How did you feel? 2) What did you learn today?
3) What will you do differently tomorrow?
www.mozaicworks.com
Code retreatWhy?
Learn through pairingExtend your comfort zone
PracticeExperiment
Learn new practices
www.mozaicworks.com
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
Code retreatExtend your mentoring & training capacity
Accelerate learning through communities of practice
Grow your functional leaders and top talents
http://www.mozaicworks.com
@adibolb