Coding Dojointroduction

Hugo Corbucci (hugo@agilbits.com.br)

Async's Team

(www.async.com.br)based on Danilo T. Sato's slides

Motivation

Programers don't practice!

Background

Kata » Coding Dojo

Principles

Continuous Learning

Safe environment:– Non Competitive

– Collaborative

– Inclusive

Fail & Redundancy

Baby steps

General Rules

Computer + Projector

TDD (red » green » refactor)

Everyone should understand

ALWAYS start fromscratch

Retrospective

At the end of all meeting:– “What did we learned?”

or “What did we liked?”

– “What could havebeen better?”

– Discussions or comments

Formats Kata

– Presentation of a solution

– Everyone should beable to reproduce

– Interruptions areallowed at anymoment to askquestions

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

Goals

Practice

Learn

Teach

Discuss withCONCRETEbasis

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

Schedule

14h00 14h50 Dojo presentation

15h00 15h20 Problem presentation

15h20 16h30 Programming

16h30 17h00 Retrospective

17h00 ... More programming?