Download to read offline
Uploaded byJohannes Brodwall
Agile Programming Live - AgilePrague2012
1) The document discusses principles of agile programming such as pair programming, test-driven development, and refactoring. 2) It describes a demonstration of test-driven development using a minesweeper game, highlighting how tests are written first and then code is produced to pass those tests. 3) The document emphasizes that practicing these agile techniques through deliberate practice of coding katas can help programmers improve their skills and "think better" above just the code level. Regular practice is encouraged at meetups like the Prague Coding Dojo.
More Related Content
Similar to Agile Programming Live - AgilePrague2012
Agile Programming Live - AgilePrague2012
- 1. Shut up andproduce…
- 2. Agile Programming Live AgilePrague 2012 Johannes Brodwall Steria Norway @jhannes
- 3. Goal • To have fun now! • For you to have fun now! • For you to have fun later (stretch goal)
- 4. Agenda • What is«agile programming» •What to look for •Demonstration •Discussion •Possibly: Tips and tricks
- 5.
- 6.
- 7.
- 10. Ingredience #2: Test driven development
- 11. Failing test Write code Failing test Write code Failing test
- 12. Ingredience #3: Refactoring
- 13. Failing test Write code Refactor code and tests Failing test Write code Refactor code and tests Failing test
- 14.
- 15. Failing test Write code Failing test Write code Failing test
- 16. Failing test Write code Refactor code and tests Failing test Write code Refactor code and tests Failing test
- 17. What do youthink? • Do you work like this? • Faster or slower? • Better code or worse? • Other effects?
- 18.
- 19. What to watchfor?
- 20. If you’re aproject manager
- 21. If you’re anarchitect
- 22. If you’re adeveloper
- 23.
- 24. Please: • Talk aboutwhat you see to the person next to you (whisper) •Tweet to @jhannes and @OlegSmirsky
- 25.
- 26.
- 29. What did yousee?
- 30. 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?
- 31. What do youthink? •Pairing two seniors? •Pairing two juniors? • Pairing senior and talent? • Pairing senior and junior?
- 32. 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?
- 33. 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?
- 34.
- 35. Why become betterat programming?
- 36.
- 37. Only 13.37% ofeffort
- 38.
- 39. Getting better quality Correctness Maintainability
- 40.
- 41.
- 42. Think better Think abovethe curly brackets
- 43. How to getbetter
- 44.
- 45.
- 46. Practice Practice at work Practice katas Practice in dojos
- 47.
- 52. Prague Coding Dojo http://agileprague.com/workshops.htm
- 53. You can stillsign up
- 54.
- 55.
- 56. Free your mind Practice our art
- 57. Thank you johannes@brodwall.com http://johannesbrodwall.com http://twitter.com/jhannes http://twitter.com/OlegSmirsky
Editor's Notes
- #28 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
- #30 Note to translator: Here, Iwill ask the English speakingmembersoftheaudience to give feedback onwhattheysaw. I will hand outchocolates to those to answer.