The document outlines the agenda for a coding dojo meeting focused on deliberate practice. It includes an introduction to deliberate practice, rules and code of honor for the dojo. The agenda then details two prepared katas, a description of group katas including Randori and Kake, and closes with a raffle and concluding remarks.
2. Deliberate Practice
Practice is the act of rehearsing a behavior over and over, or
engaging in an activity again and again, for the purpose of
improving or mastering it.
An expert breaks down the skills that are required to be
expert and focuses on improving those skill chunks during
practice or day-to-day activities, often paired with immediate
coaching feedback.
Continually practicing a skill at more challenging levels with
the intention of mastering it.
3. Deliberate Practice
A Coding Dojo is Deliberate Practice for Software Developers
But is a team (group) activity
It must be fun
It accepts all knowledge levels
Immediate Feedback: That’s why TDD gets so used
Focus on core skills not so much in tools
Mixed skill levels => Guidance from more experienced developers
4. Agenda: Intro and Prepared Katas
Early Arrival and Registration 6:45 p.m. to 7:05 p.m.
Intro, Rules, and Dynamics (05 min) 7:05 p.m. to 7:10 pm.
First Prepared Kata (15 min): 7:10 p.m. to 7:25 p.m.
Second Prepared Kata (15 min): 7:25 p.m. to 7:40 p.m.
Kata format description Radonri and Kake (10 min) : 7:40 p.m. to 7:50 p.m.
5. Agenda: Group, Raffle, and Closing
Group Kata (a) Kake (55 min)
Work (40 min): 7:50 p.m. to 8:30 p.m.
Solutions review (15 min): 8:30 p.m. to 8:45 p.m.
Group Kata (b) Randori (55 min): 7:50 p.m. to 8:45 p.m.
Raffle (5 min): 8:45 p.m. to 8:55 p.m.
Closing (5 min): 8:55 p.m. to 9:00 p.m.
6. Agenda: 00% (6:45 to 07:05)
Radonri & Kake
Description: 42%
Group Kata: 88% Raffle: 96% Closing: 100%
Arrival &
Registration: 0%
Intro, Rules, &
Dynamics: 8%
Prepared Kata
01: 21%
Prepared Kata
02: 33%
7. Intro, Rules, and Dynamics
Tech stuff first
GitHub repo kodisto-dojo/dr_open_dojos (read only)
Flow: Fork => Work => Pull Request
Read the README.md file for more details
Do not loose time with this, work freely at the Dojo,
then upload code from home / work
8. Intro, Rules, and Dynamics: Code Of Honor
NO Bullying
Criticize Ideas not People
Stay focus: ovoid unnecessary distractions
Dojos are Secular (like a Secular State):
to be officially neutral in matters of religion
9. Intro, Rules, and Dynamics: Code Of Honor
What is a religion for us?
Programming Languages
Vendors
Tools
Frameworks, etc.
Focus on developing your practice
(craftsmanship)
Don't be a "Tool guru“
Don't be a "Vendor Evangelizer"
10. Intro, Rules, and Dynamics: Code Of Honor
Prepared Kata Rules: Authors
Allow questions and short interruptions
Practices before the event
Explain the problem
Explain the solution approach
Stick to the time-box
Prepared Kata Rules: Audience
Wait for proper moment to ask or
comment
If you think you can do better prepare
one for next event
Don’t try to force the author to follow
your proposal
16. Randori and Kake description
Randori
Single problem
Single group (everyone)
Single machine + Digital Projector
Always a pair on the keyboard
Pilot / Driver + Co-Pilot
At the end we do a little retrospective
Kake
Single problem
Many groups (2 to 4) people
Each group with a different language (if
possible)
Present each solution at the end
Each group must explain their approach
17. Randori and Kake description
Randori details
If you have the keyboard, you get to
decide what to type
If you have the keyboard and you don’t
know what to type, ask for help
If you are asked for help, kindly respond
to the best of your ability
If you are not asked, but you see an
opportunity for improvement / learning,
choose an appropriate moment to
mention it
Wait until the next time all the tests
pass
Or until the retrospective
19. Group Kata
If Randori
Rotate every N minutes / N Tests
Kata Options
01-Raffle API
02-String Calculator
03-Roman Numerals
04-Command Line Args
Schema + Parser
05-Console Personal Assistant
V01: Single Call + Range evaluator +
Simple calculator + Temp converter
V02: Add an Interactive Interpreter
(REPL => read–eval–print loop)
21. Raffle Time
Remember
One (first) ticket if you are here at Raffle’s
time (now)
+1 Ticket: If you get early to the event 15
mins before or exactly at start time
+1 Ticket: If you do a Prepared Kata
Rules
You must be present to participate
Only one gift per person
Software
We’ll use only tools developed by the
group
23. Closing Words
Next meeting
When? Thu Feb. 04 2016
What time? 07:00 p.m. to 09:00 p.m.
Where? Same place until further notice
Remember to …
Upload the code to the GitHub repo
Share any pictures / screen casts
Invite friends and coworkers