The document outlines the concept of a coding dojo, a collaborative environment where programmers train and learn together through pair programming. It describes pair programming roles (driver and observer), techniques such as test-driven development (TDD), and the retrospective process for continuous improvement. Additionally, it includes links to resources and emphasizes the non-competitive, educational focus of a coding dojo.

1. Coding-Dojo Wouter Lagerweij wlagerweij@qualogy.com, www.lagerweij.com, @wouterla http://www.tierrapura.org/construccion/dojo.jpg Original presentation by Serge Rehem [email_address]

2. Programmers don't train.

3. Coding Dojo http://pt.wikipedia.org/wiki/Ficheiro:Noma_Dojo,_2006.JPG programmers gather to train and learn , work together on a problem

4. Dojo NOT a competition or a show

5. Pair Programming

6. Pair Programming Driver/Observer (one has the keyboard) Driver has keyboard

7. Observer can watch bigger picture One writes test, Other fixes (ping-pong)

8. Talk out loud about what you're doing

9. Wait for green to comment

10. Keep list of what to do next (observer -> flip-over)

11. red - green - refactor T D D

12. Baby Steps

14. Prepared Kata driver/observer fixed solved before, performed live

15. http://dojorio.wordpress.com/2009/05/11/coding-dojo-rio-na-pythoncampus-na-universidade-gama-filho-no-campus-da-piedade/ Randori Kata driver/observer switch , every 5 to 10 mins. problem solved live

16. What went well? What didn't? What did we learn? retrospective http://blog.seatecnologia.com.br/tag/dojo

17. Esta obra está licenciada sob uma Licença Creative Commons http://creativecommons.org/licenses/by-nc-sa/2.0/br/

18. Serge Rehem [email_address] twitter.com/serge_rehem slideshare.net/serge_rehem groups.google.com.br/group/dojo-bahia Obrigado!