Download to read offline
Uploaded byJohannes Brodwall
2013 09-11 java zone - extreme programming live
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.
More Related Content
Similar to 2013 09-11 java zone - extreme programming live
![[IJCT-V3I2P28] Authors: KulbirKaur, AnureetKaur](https://cdn.slidesharecdn.com/ss_thumbnails/ijct-v3i2p28-160609063624-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
2013 09-11 java zone - extreme programming live
- 1. Extreme Programming Live JavaZone 2013 JohannesBrodwall Exilesoft Chief scientist @jhannes
- 2. How do youbecome 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. Whatto look for 3. Demonstration 4. Discussion 5. Conclusion
- 5.
- 6. It is betterto • Do the thing right, then to • Do the right thing • (first)
- 7.
- 8.
- 11.
- 12. Failing test Write code Failingtest Write code Failing test
- 13.
- 14. Failing test Write code Failingtest Write code Failing test Refactor code and tests Refactor code and tests
- 15.
- 16. Failing test Write code Failingtest Write code Failing test
- 17. Failing test Write code Failingtest Write code Failing test Refactor code and tests Refactor code and tests
- 18. Failing test Write code Failingtest Write code Failing test Refactor code and tests Refactor code and tests
- 19.
- 20. What to watchfor?
- 21. What to watchfor? • How do we work together? • How do we use tests to understand? • How do we «grow» the code?
- 22. Please: • Talk aboutwhat you see to the person next to you (whisper) •Tweet to @jhannes and @erlingwl
- 23. Demonstration (Guest starring RoyFernando)
- 24.
- 27. What did yousee?
- 28. What did yousee? • 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 youthink? •Pairing two seniors? •Pairing two juniors? • Pairing senior and talent? • Pairing senior and junior?
- 30. What did yousee? • 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 yousee? •Did we refactor the right amount? • How long was the code red? • Strengths in final design •Weaknesses in final design •Enough comments?
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41. Think better Think beyondthe curly brackets
- 42. How to getbetter
- 43.
- 44. Deliberate Practice • Slowdown • Repeat • Reflect
- 45.
- 46. Practice at work •Tests lets you solve it faster
- 47.
- 48.
- 49.
- 55. What have youlearned • 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 differentLevels of quality
- 57.
- 58.
- 59. Free your mind Practiceour art
- 60.
Editor's Notes
- #26 Note to translator: I willexplainthe game of minesweeper whileshowingthis slide.The game initiallypresents a fieldwheretherearehidden minesWhentheplayerclickson a cell, eitherhe «steps» on a mine or he reveals thecellIf he «stepson a mine», the game is over, player losesIf he reveals thecell, thecelltellshowmany mines arenext to it
- #28 Note to translator: Here, Iwill ask the English speakingmembersoftheaudience to give feedback onwhattheysaw. I will hand outchocolates to those to answer.