1 / 57

Extreme Programming Live

Extreme Programming Live. WeActuallyBuildStuff Johannes Brodwall Exilesoft Chief scientist @ jhannes. Guest starring: Chaminda Sooriyapperuma. How do you become a better programmer. After this talk You may find desire to train with TDD You may pair program sometimes

fleur-mcconnell
Télécharger la présentation

Extreme Programming Live

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Extreme Programming Live WeActuallyBuildStuff Johannes Brodwall Exilesoft Chief scientist @jhannes Guest starring: Chaminda Sooriyapperuma

  2. How do you become a better programmer

  3. After this talk You may find desire to train with TDD You may pair program sometimes You may think of some ways to improve the way you work

  4. Waddayamean«extreme programming» What to look for Demonstration Discussion Conclusion

  5. «Extreme programming»?

  6. It is better to Do the thing right, then to Do the right thing (first)

  7. Pingpong

  8. Ingredience #1: Pair programming

  9. Ingredience #2: Test driven development

  10. Failing test Write code Failing test Write code Failing test

  11. Ingredience #3: Refactoring

  12. Failing test Write code Refactorcode and tests Failing test Write code Refactorcode and tests Failing test

  13. Puttogether

  14. Failing test Write code Failing test Write code Failing test

  15. Failing test Write code Refactorcode and tests Failing test Write code Refactorcode and tests Failing test

  16. Failing test Write code Refactorcode and tests Failing test Write code Refactorcode and tests Failing test

  17. Demonstration

  18. What to watch for?

  19. What to watch for? How do we work together? How do weuse tests to understand? How do we «grow» thecode?

  20. Please: Talk aboutwhatyousee to the person next to you (whisper) Tweet to @jhannes

  21. Demonstration (Guest starring Chaminda Sooriyapperuma)

  22. Kata: Prime factors

  23. Kata: Prime factors 1 => [] 2 => [2] 3 => [3] 4 => [2,2] … 2*2*13*17*23*23 => [2,2,13,17,23,23]

  24. Whatdidyousee?

  25. Whatdidyousee? Howoftendidweswitch ”driver”? Effectsofpairing? Whatdidthe ”non-driver” do? How do youexpect it to be different?

  26. What do youthink? Pairingtwo seniors? Pairingtwojuniors? Pairing senior and talent? Pairing senior and junior?

  27. Whatdidyousee? How many tests? Wasthestepsize right? Whatwasthe first test? Howdidwedecidenext test? Whatwasthe final test?

  28. Whatdidyousee? Didwerefactorthe right amount? Howlongwasthecode red? Strengths in final design Weaknesses in final design Enoughcomments?

  29. Questions? Your experience?

  30. Becoming a better programmer

  31. Why become better programmer?

  32. Gettingbetterquality

  33. Gettingbetterquality Correctness Maintainability Productivity

  34. But more importantly!

  35. Thinkbetter

  36. Thinkbetter Think beyond the curly brackets

  37. How to getbetter

  38. Practice

  39. Deliberate Practice Slow down Repeat Reflect

  40. Practice at school

  41. Practice at school Tests lets you solve it faster

  42. Practice at home

  43. Practice at home Learn more here

  44. Practice with friends

More Related