This group was started to organize a Coding Dojo in Wellington. The main focus is on Java and Java-related technologies (Groovy, Grails, Scala...), though other technologies are welcome as well.

A Coding Dojo is a place where programmers come to improve their skills, by following a pattern similar to the martial arts dojo. Patricipants meet for at a pre-arranged time in a room that has one computer attached to a screen. A programming challenge is posed for each session. There are a couple of ways this is done that will be discussed later. During the session, the group spends a pre-set amount of time developing a solution to the challenge. At the end of the ssession the code is discarded (often it is archived for future reference and study). The amount of time spent on the problem is fixed. Regardless of the state of the solution, when the time expires, the session is done.

The rules and sample session agenda presented here are preliminary and will be changed based on the experience gathered from previous sessions: * There is a coding challenge that is announced beforehand. * There is a room with one computer attached to video screen. * The presenter explains the coding challenge and starts the coding. The presenter may or may not choose to have a co-pilot. A co-pilot is usually assigned so that when the switch occurs, the co-pilot takes over for the coder. * One half of the pair is changed every 5 minutes. * The coder should continuously explain what she or he is doing. * The coder should stop when someone from the audience falls off the sled (has a question about understanding what the pair is doing) -- and only continue when that someone is back on track again. * All coders use TDD (Test-Driven Development). * All produced code will be made publicly available using the Eclipse Common Public License. * The programming language to be used is announced in advance per session.