The document summarizes an "Extreme Programming" talk given by Johannes Brodwall. The talk demonstrates test-driven development and pair programming. It discusses the benefits of these practices, such as producing higher quality code through simplicity, communication, and feedback. It encourages programmers to practice deliberately, both at work and at home, in order to continuously improve. The conclusion emphasizes freeing the mind and practicing programming as an art.

1. Extreme Programming
Live
JavaZone 2013
Johannes Brodwall
Exilesoft Chief scientist
@jhannes

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
Refactor code
and tests

15. Put together

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

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

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

19. Demonstration

20. What to watch for?

21. What to watch for?
• 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 and @erlingwl

23. Demonstration
(Guest starring Roy Fernando)

24. Kata: Minesweeper

27. What did you see?

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

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

30. 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?

31. 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?

32. XP values

33. XP values
Simplicity
Communication
Feedback
Communication

34. Questions?
Your experience?

35. Becoming a better
programmer

36. Why become better
programmer?

37. Getting better quality

38. Getting better quality
Correctness
Maintainability
Productivity

39. But more importantly!

40. Think better

41. Think better
Think beyond the curly brackets

42. How to get better

43. Practice

44. Deliberate Practice
• Slow down
• Repeat
• Reflect

45. Practice at work

46. Practice at work
• Tests lets you solve it faster

47. Practice at home

48. Practice at home
Learn
more here

49. Practice with friends

55. 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

56. +
TDD & different
different Levels of
quality

57. Conclusion

58. Conclusion
Free your mind

59. Free your mind
Practice our art

60. jbr@exilesoft.com
erling@cvpartner.com
http://johannesbrodwall.com
http://exilesoft.com
http://twitter.com/jhannes
http://twitter.com/erlingwl
Thank you