2011 09-17 tampere - the practicing programmer

707 views

Published on

Tampere Goes Agile: The Practicing Developer

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

2011 09-17 tampere - the practicing programmer

  1. 1. The practicing programmer<br />TampereGoes Agiles<br />Johannes Brodwall, Just-a-programmer<br />SteriaNorway<br />
  2. 2. The Practicing Programmer<br />
  3. 3. PracticingProgramming<br />
  4. 4. How to workbetter<br />How to learnbetter<br />
  5. 5. Test-first<br />XP Explained 1sted<br />On-sitecustomer<br />CI<br />Simple design<br />40-hour week<br />Frequentreleases<br />Collectiveownership<br />Refactoring<br />Metaphor<br />Code standard<br />Pairing<br />The planning game<br />
  6. 6. Test-first<br />On-sitecustomer<br />CI<br />Simple design<br />40-hour week<br />Frequentreleases<br />Collectiveownership<br />Refactoring<br />Metaphor<br />Code standard<br />Pairing<br />The planning game<br />
  7. 7. Test-first<br />On-sitecustomer<br />CI<br />Simple design<br />40-hour week<br />Frequentreleases<br />Collectiveownership<br />Refactoring<br />Metaphor<br />Code standard<br />Pairing<br />The planning game<br />
  8. 8. Demo<br />
  9. 9. Whatdidyousee?<br />
  10. 10. Whendidweswitch ”driver”?<br />Effectsofpairing?<br />Howmany tests?<br />Test frequency<br />IDE tricks<br />Stepsize? Toosmall? Toobig?<br />Whendidwerefactor?<br />First test?<br />Pickingnext test?<br />Final test?<br />
  11. 11. Test-first<br />On-sitecustomer<br />CI<br />Simple design<br />40-hour week<br />Frequentreleases<br />Collectiveownership<br />Refactoring<br />Metaphor<br />Code standard<br />Pairing<br />The planning game<br />
  12. 12. Whybecomebetter at programming?<br />
  13. 13. Seriously. Why?<br />
  14. 14. Only 13.37% ofeffort<br />
  15. 15. Gettingbetterquality<br />
  16. 16. Gettingbetterquality<br />Correctness<br />Maintainability<br />
  17. 17. But more importantly!<br />
  18. 18. Thinkbetter<br />
  19. 19. Thinkbetter<br />Raiseyourlevelofabstraction<br />
  20. 20. What to practice<br />
  21. 21. Test thecontract<br />
  22. 22. Test thecontract<br />API<br />Not behavior<br />
  23. 23.
  24. 24. Test from outside-in<br />
  25. 25. Test from outside-in<br />Who?<br />Why?<br />Pop!<br />Mock<br />
  26. 26.
  27. 27. TODO: Bilde av standup og tavle<br />Konfidensiell - Navn på presentasjon.ppt<br />17.09.2011<br />27<br />
  28. 28. Practice pair programming<br />
  29. 29. Pingpong<br />
  30. 30. Failing test<br />Fixthe test<br />Failing test<br />Fixthe test<br />Failing test<br />
  31. 31. Failing test<br />Fixthe test<br />Refactor<br />Failing test<br />Fixthe test<br />Refactor<br />Failing test<br />
  32. 32. Johannes<br />Jussi<br />Katja<br />Ari<br />Vlad<br />
  33. 33. Johannes<br />Jussi<br />Katja<br />Ari<br />Vlad<br />
  34. 34. Johannes<br />Jussi<br />Katja<br />Ari<br />Vlad<br />
  35. 35. All-greenrefactoring<br />
  36. 36. All-greenrefactoring<br />Reducethe time ofuncertainty<br />
  37. 37. Continuousintegration<br />
  38. 38. Continuousintegration<br />Avoidbranching<br />Run tests all the time<br />
  39. 39.
  40. 40. Pick a demo<br />
  41. 41. Pick a demo<br />Outside-in<br />Mocking<br />Contract test<br />All-greenrefactoring<br />Continuousintegration<br />
  42. 42. How to practice<br />
  43. 43. Practice<br />Practicekatas<br />Practice at work<br />Practice in dojos<br />
  44. 44. Conclusion<br />
  45. 45. Conclusion<br />Freeyourmind<br />
  46. 46. Freeyourmind<br />Practiceour art<br />
  47. 47. Thankyou<br />johannes.brodwall@steria.no<br />http://johannesbrodwall.com<br />http://twitter.com/jhannes<br />

×