Code retreat june24th
Upcoming SlideShare
Loading in...5
×
 

Code retreat june24th

on

  • 790 views

Slides supporting our June 24th 2011 CodeRetreat at Xebia TechEvent.

Slides supporting our June 24th 2011 CodeRetreat at Xebia TechEvent.

Statistics

Views

Total Views
790
Views on SlideShare
781
Embed Views
9

Actions

Likes
3
Downloads
10
Comments
0

3 Embeds 9

http://coderwall.com 7
https://twitter.com 1
http://twitter.com 1

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Code retreat june24th Code retreat june24th Presentation Transcript

  • Code Retreatjune 24th 2011 - XEBIA
  • Welcome
  • Deliberate Practice Improve ability to perform a task Repetition, repetition, repetition... Not complete the task, but master it. View slide
  • Simple DesignRun all tests and check they pass.Dont Repeat YourselfReveal intentSmall methods & classes View slide
  • Open your mind !Try things you cant try @ work.Do silly things that just *cant* work...Explore, experiment.Pair with as much people as you canDont be shy, try new languages.
  • Introduction a session lasts 40 minutes followed by a 10-15 minutes retrospective pair programming swap on each session delete all code after each session
  • Planning10h00 14h00 Code Session 1 Code Session 4 Retrospective 1 Retrospective 411h00 15h00 Code Session 2 Code Session 5 Retrospective 2 Retrospective 512h00 16h00 Code Session 3 Code Session 6 Retrospective 3 16h4013h00 Day Retrospective ... Lunch14h00
  • TicTacToe
  • TicTacToe rules1. a game is over when all fields are taken2. a game is over when all fields in a column are taken by a player3. a game is over when all fields in a row are taken by a player4. a game is over when all fields in a diagonal are taken by a player5. a player can take a field if not already taken6. players take turns taking fields until the game is over
  • Session #1 10h00 10h401. a game is over when all fields are taken2. a game is over when all fields in a column are taken by a player3. a game is over when all fields in a row are taken by a player4. a game is over when all fields in a diagonal are taken by a player5. a player can take a field if not already taken6. players take turns taking fields until the game is over
  • Rétro #1 10h40 11h00Does your code work at the end of the session ?What is your implementation path ?How was your pair programming experience ?How was your TDD experience ? How did it help ?Did you notice any code smells ?Did you notice any communication smells ?Any tips for the others ?
  • Session #2 11h00 11h401. a game is over when all fields are taken2. a game is over when all fields in a column are taken by a player3. a game is over when all fields in a row are taken by a player4. a game is over when all fields in a diagonal are taken by a player5. a player can take a field if not already taken6. players take turns taking fields until the game is over
  • Rétro #2 11h40 12h00Does your code work at the end of the session ?What is your implementation path ?How was your pair programming experience ?How was your TDD experience ? How did it help ?Did you notice any code smells ?Did you notice any communication smells ?Any tips for the others ?
  • Session #3 12h00 12h401. a game is over when all fields are taken2. a game is over when all fields in a column are taken by a player3. a game is over when all fields in a row are taken by a player4. a game is over when all fields in a diagonal are taken by a player5. a player can take a field if not already taken6. players take turns taking fields until the game is over
  • Rétro #3 12h40 13h00Does your code work at the end of the session ?What is your implementation path ?How was your pair programming experience ?How was your TDD experience ? How did it help ?Did you notice any code smells ?Did you notice any communication smells ?Any tips for the others ?
  • Lunch Time !
  • Session #4 14h00 14h40 1. a game is over when all fields are taken 2. a game is over when all fields in a column are taken by a player 3. a game is over when all fields in a row are taken by a player 4. a game is over when all fields in a diagonal are taken by a player 5. a player can take a field if not already taken 6. players take turns taking fields until the game is overTDD as you meant it || No mouse || Switch keyb.
  • TDD AS YOU MEANT IT1. write exactly ONE failing test2. make this test pass by first writing implementation code IN THE TEST METHOD3. create a new implementation method by: 1. doing extract method on implementation code created as per (2), or 2. moving implementation code as per (2) into an existing implementation method4. only ever create new methods IN THE TEST CLASS5. only ever create implementation classes to provide a destination for extracting a method created as per (4).6. populate implementation classes by doing move method from a test class into them7. refactor as required8. go to (1)
  • Rétro #4 14h40 15h00Does your code work at the end of the session ?What is your implementation path ?How was your pair programming experience ?How was your TDD experience ? How did it help ?Did you notice any code smells ?Did you notice any communication smells ?Any tips for the others ?
  • Session #5 15h00 15h401. a game is over when all fields are taken2. a game is over when all fields in a column are taken by a player3. a game is over when all fields in a row are taken by a player4. a game is over when all fields in a diagonal are taken by a player5. a player can take a field if not already taken6. players take turns taking fields until the game is over No Loops || No if(s) || Small methods (<5)
  • Rétro #5 15h40 16h00Does your code work at the end of the session ?What is your implementation path ?How was your pair programming experience ?How was your TDD experience ? How did it help ?Did you notice any code smells ?Did you notice any communication smells ?Any tips for the others ?
  • Session #6 16h00 16h401. a game is over when all fields are taken2. a game is over when all fields in a column are taken by a player3. a game is over when all fields in a row are taken by a player4. a game is over when all fields in a diagonal are taken by a player5. a player can take a field if not already taken6. players take turns taking fields until the game is over No Loops || No if(s) || Small methods (<5)
  • Day RetrospectiveWhat did you learn today ?What were you surprised about today ?What will you apply starting Monday ?