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. 1.Waddayamean «extreme programming» 2.What to look for 3.Demonstration 4.Discussion 5.Conclusion

5. «Extreme programming»?

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

7. Ping pong

8. Ingredient #1: Pair programming

11. Ingredient #2: Test driven development

12. Failing test Write code Failing test Write code Failing test

13. Ingredient #3: Refactoring

14. Failing test Write code Failing test Write code Failing test Refactor code and tests

15. Put together

16. Failing test Write code Failing test Write code Failing test

17. Write code Failing test Write code Failing test Refactor code and tests

18. Failing test Write code Failing test Write code Failing test Refactor code and tests

19. Demonstration

20. What to watch for?

21. How do we work together? How do we use tests to understand? How do we «grow» the code?

22. Please: Talk about what you see to the person next to you (whisper) Tweet to @jhannes

23. Demonstration (Guest starring Chaminda Sooriyapperuma)

24. Kata: Prime factors

25. 1 => [] 2 => [2] 3 => [3] 4 => [2,2] … 2*2*13*17*23*23 => [2,2,13,17,23,23]

26. What did you see?

27. How often did we switch ”driver”? Effects of pairing? What did the ”non-driver” do? How do you expect it to be different?

28. What do you think? Pairing two seniors? Pairing two juniors? Pairing senior and talent? Pairing senior and junior?

29. What did you see? How many tests? Was the step size right? What was the first test? How did we decide next test? What was the final test?

30. What did you see? Did we refactor the right amount? How long was the code red? Strengths in final design Weaknesses in final design Enough comments?

31. Questions? Your experience?

32. Becoming a better programmer

33. Why become better programmer?

34. Getting better quality

35. Correctness Maintainability Productivity

36. But more importantly!

37. Think better

38. Think beyond the curly brackets

39. How to get better

40. Practice

41. Deliberate Practice Slow down Repeat Reflect

42. Practice at school

43. Tests lets you solve it faster

44. Practice at home

45. Learn more here

46. Practice with friends

52. What have you learned TDD makes you productive TDD consists of small steps TDD requires practice Pair programming is fun Pair programming helps you keep flow

53. + TDD & different different Levels of quality

54. Conclusion

55. Free your mind

56. Practice our art

57. jbr@exilesoft.com cgu@exilesoft.com http://johannesbrodwall.com http://exilesoft.com http://twitter.com/jhannes Thank you