Agile Programming Live - AgilePrague2012
•Transferir como PPTX, PDF•
1 gostou•463 visualizações
Agile Programming Lig
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Semelhante a Agile Programming Live - AgilePrague2012
Semelhante a Agile Programming Live - AgilePrague2012 (20)
Mais de Johannes Brodwall
Mais de Johannes Brodwall (13)
Último
Último (20)
Agile Programming Live - AgilePrague2012
- 1. Shut up and produce…
- 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
- 6. Ping pong
- 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. Put together
- 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 you think? • Do you work like this? • Faster or slower? • Better code or worse? • Other effects?
- 18. Demonstration
- 19. What to watch for?
- 20. If you’re a project manager
- 21. If you’re an architect
- 22. If you’re a developer
- 24. Please: • Talk about what you see to the person next to you (whisper) •Tweet to @jhannes and @OlegSmirsky
- 29. What did you see?
- 30. 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?
- 31. What do you think? •Pairing two seniors? •Pairing two juniors? • Pairing senior and talent? • Pairing senior and junior?
- 32. 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?
- 33. 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?
- 35. Why become better at programming?
- 36. Seriously. Why?
- 37. Only 13.37% of effort
- 39. Getting better quality Correctness Maintainability
- 41. Think better
- 42. Think better Think above the curly brackets
- 43. How to get better
- 44. Practice
- 46. Practice Practice at work Practice katas Practice in dojos
- 52. Prague Coding Dojo http://agileprague.com/workshops.htm
- 53. You can still sign up
- 54. Conclusion
- 55. Conclusion Free your mind
- 56. Free your mind Practice our art
- 57. Thank you johannes@brodwall.com http://johannesbrodwall.com http://twitter.com/jhannes http://twitter.com/OlegSmirsky
Notas do Editor
- 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
- Note to translator: Here, Iwill ask the English speakingmembersoftheaudience to give feedback onwhattheysaw. I will hand outchocolates to those to answer.