Download to read offline
![Given:
var minefield = new Minefield([
"....",
".*..",
".*.*",
"...*“ ])](https://image.slidesharecdn.com/2011-12-17xpdaysukraine-experienceagiledevelopment-111220054528-phpapp02/85/Experience-Agile-Programming-Kiev-7-320.jpg)
![Given:
var minefield = new Minefield([
"....",
".*..",
".*.*",
"...*“ ])](https://image.slidesharecdn.com/2011-12-17xpdaysukraine-experienceagiledevelopment-111220054528-phpapp02/75/Experience-Agile-Programming-Kiev-7-2048.jpg)
Uploaded byJohannes Brodwall
Experience Agile Programming - Kiev
This document summarizes an Agile programming experience day in Ukraine. The goal is for attendees to have fun programming now and to think better by practicing their skills. The agenda includes a description of a minesweeper coding kata demonstration featuring pair programming. Attendees are encouraged to observe how the pair interacts, designs the code, and progresses through testing. The benefits of practices like test-driven development, pairing, and refactoring are discussed. The conclusion encourages practicing programming skills at work, with coding dojos, and by freeing the mind.
More Related Content
Similar to Experience Agile Programming - Kiev
More from Johannes Brodwall
Experience Agile Programming - Kiev
- 1. Experience Agile Programming XP Days Ukraine Йоханнес Бродвалл, Just-a-programmer Стерия Норвегия @jhannes
- 2. Goal • To have fun now! • For you to have fun now! • For you to have fun later (stretch goal)
- 3. Agenda • Description •Demonstration with Dima Mindra • Discussion • Tips and tricks
- 4.
- 5.
- 7. Given: var minefield =new Minefield([ "....", ".*..", ".*.*", "...*“ ])
- 8. What do watchfor • How we interact • How we progress through the code • How we design • How we use the language
- 9.
- 10. What did yousee?
- 11. What did yousee? • How often did we switch ”driver”? • Effects of pairing? • What did the ”non-driver” do?
- 12. What did yousee? • Was the step size right? • What was the first test? • How did we decide next test? • What was the final test?
- 13. What did yousee? • Language tricks? • Did we refactor the right amount? • How long was the code red? • Strengths in final design •Weaknesses in final design
- 14. Why become betterat programming?
- 15.
- 16. Only 13.37% ofeffort
- 17.
- 18. Getting better quality Correctness Maintainability
- 19.
- 20.
- 21. Think better Raise yourlevel of abstraction
- 22.
- 23.
- 24. Test the contract API Not behavior
- 26.
- 27. Test from outside-in Who? Why? Pop! Mock
- 29.
- 30.
- 31. Failing test Fix the test Failing test Fix the test Failing test
- 32. Failing test Fix the test Refactor Failing test Fix the test Refactor Failing test
- 33. Johannes Dmytro Mikhail Sergey Volodymyr
- 34. Johannes Dmytro Mikhail Sergey Volodymyr
- 35. Johannes Dmytro Mikhail Sergey Volodymyr
- 36.
- 37. All-green refactoring Reduce the time of uncertainty
- 38.
- 39. Practice Practice at work Practice katas Practice in dojos
- 40.
- 44.
- 45.
- 46. Free your mind Practice our art
- 47. Thank you johannes.brodwall@steria.no http://johannesbrodwall.com http://twitter.com/jhannes (Please tweet in Cyrillic with english-like words)