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 continuously learn, teach, and discuss concrete coding problems. Formats include katas, where a presenter demonstrates a solution step-by-step, and randori, where participants take turns pairing on time-boxed coding problems while others observe and provide feedback. Retrospectives are held at the end to discuss learnings and improvements. The aim is to practice skills through failure and redundancy rather than rushing to finish or competing against others.
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