The document summarizes an "Extreme Programming" talk given by Johannes Brodwall. The talk introduces concepts like test-driven development (TDD), pair programming, and refactoring. A demonstration of pair programming on a coding kata is shown. The key points emphasized are that practicing TDD in small iterative steps, pairing with others, and continuously refactoring code can help programmers improve quality and think in a more deliberate, mindful way about their work. The overall message is that becoming a better programmer requires freeing one's mind and practicing programming as an art.

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

2. Goal
• To have fun now!
• For you to have fun now!
• For you to have fun later
(stretch goal)

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. Is it better to
• Do the thing right?
• Do the right thing?

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

9. Ping pong

10. Ingredience #1:
Pair programming

13. Ingredience #2:
Test driven
development

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

15. Ingredience #3:
Refactoring

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

17. Put together

18. Failing test
Write code
Failing test
Write code
Failing test

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

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

21. Demonstration

22. What to watch for?

23. If you’re a project manager

24. If you’re an architect

25. If you’re a developer

26. If you’re neither

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

28. Demonstration
(Guest starring Andrej Slivko)

29. Kata: Minesweeper

32. What did you see?

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

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

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

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

37. Questions?
Your experience?

38. Becoming a better
programmer

39. Why become better
programmer?

40. Seriously. Why?

41. Only 13.37% of effort

42. Getting better quality

43. Getting better quality
Correctness
Maintainability

44. But more importantly!

45. Think better

46. Think better
Think beyond the curly brackets

47. «The Alignment Trap»

48. How to get better

49. Practice

50. Deliberate Practice
• Slow down
• Repeat
• Reflect

51. Practice at work

52. Practice at home

53. Practice at home
Watch this
space!

54. Practice with friends

55. Vilnius Coding Dojo?

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

62. Conclusion

63. Conclusion
Free your mind

64. Free your mind
Practice our art

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