• Like
Coding Dojo
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Coding Dojo


December '09 …

December '09
OrlandoPHP user group meeting

Published in Technology , Design
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • coding for a client is not practice; deadlines; interruptions; usually rushing through things;
    how to practice?
  • Dave Thomas suggested the term ‘Kata’ for programming exercises
  • practice exercises; no interruptions; slow; with feedback / mentoring;
    no deadline;
  • work with different people;
  • work with different people;
  • it is ok not to get to the solution;
  • no one is being fired for making mistakes or asking for help;
    everyone’s welcome to help; all skill levels are welcome
  • usually come with restrains;
    harder to sanitize than to come up with new problems
  • what have we learned ?
    what did we like / did not like ?
    what needs improvement ?


  • 1. Coding Dojo @caike caikesouza.com
  • 2. Coding Dojo @caike caikesouza.com
  • 3. Lack of practice
  • 4. Kata
  • 5. ( or literally: "form"): japanese word describing detailed choreographed patterns of movements practiced either solo or in pair http://en.wikipedia.org/wiki/Kata
  • 6. Dojo http://www.flickr.com/photos/el_ser_lomo/3267627038/
  • 7. Dojo get together to work on a kata, have fun and engage in deliberate practice
  • 8. Goal - practice - learn techniques - improve techniques - not necessarily solve the problem
  • 9. Values - safe environment - new ideas are welcome - collaborative / non-competitive open to all skill levels
  • 10. NO REAL WORLD PROBLEMS - context and pressure - memory requirements - performance requirements
  • 12. Kata Formats
  • 13. Prepared Kata - One presenter - Program from scratch - TDD + BabySteps - must make sense to everyone - all are welcome to ask questions
  • 14. http://www.flickr.com/photos/dtsato/1061834029
  • 15. Randori Kata - Coding pair (driver and copilot). - Everyone is invited to help. - Timebox to advance (5 - 7 minutes). - TDD + BabySteps. - Driver goes back to the audience, the copilot becomes driver and other from the audience steps up to be copilot.
  • 16. http://www.flickr.com/photos/dtsato/992058455
  • 17. http://www.flickr.com/photos/dtsato/1062695160/
  • 18. ETTIQUETE If you know how to code, you should code If you’re coding, everyone else has to understand what you’re doing If you’re the next to code, avoid breaking the flow If you’re not coding, don’t disturb who is If you have an idea, show it with code If you’re stuck, ask for help http://isanchez.net/2009/11/06/coding-dojo-etiquette
  • 19. JOIN US! http://groups.google.com/group/orlando-dojo http://orlandodojo.wordpress.com/ NEXT SESSION - NEXT THURSDAY (Dec 10) CoLabOrlando #orlando-php #orlando-dojo