This document outlines the principles and format of coding dojos, which are meetings where programmers practice coding skills together in a collaborative and non-competitive environment. The goals are to practice, learn, and teach through concrete examples using test-driven development. The general format involves presenting a problem and then taking turns programming it while others observe and provide feedback. Retrospectives are held at the end to discuss lessons learned and ways to improve.

1. Coding Dojo
introduction
Hugo Corbucci
(hugo@agilbits.com.br)
Async's Team
(www.async.com.br)
based on Danilo T.Sato's slides

2. Motivation
Programers don't practice!

3. Background
Kata » Coding Dojo

4. Principles
 Continuous Learning
 Safe environment:
– Non Competitive
– Collaborative
– Inclusive
 Fail & Redundancy
 Baby steps

5. General Rules
 Computer + Projector
 TDD (red » green » refactor)
 Everyone should understand
 ALWAYS
start from
scratch

6. Retrospective
 At the end of all meeting:
– “What did we learned?”
or “What did we liked?”
– “What could have
been better?”
– Discussions or comments

7. Formats
 Kata
– Presentation of a solution
– Everyone should be
able to reproduce
– Interruptions are
allowed at any
moment to ask
questions

8. Formats
 Randori
– Pair Programming
– Time-boxed rounds
– After each round (5-7 min.):
• The co-pilot becomes pilot
• The pilot goes back to the audience
• A new co-pilot is invited from the audience
– Comments and critics only on green
– Silence on red

9. Goals
 Practice
 Learn
 Teach
 Discuss with
CONCRETE
basis

10. Don't...
 Rush to finish the problem
 Use a real problem
 Go into flamewars on discussions
 Compete with other participants
 Allow people to get lost

11. Schedule
 14h00 14h50 Dojo presentation
 15h00 15h20 Problem presentation
 15h20 16h30 Programming
 16h30 17h00 Retrospective
 17h00 ... More programming?