Hi Todd, others,<div><br></div><div>I'm very much in favor of having a Dojo and would like to participate. I'm not too much in favor of the democratic style of decision making. So I would like to ask you to just pick a date, location and a challenge and we'll go from there. May Todd be our sensei!</div>
<div><br></div><div>If you want a location I might be able to arrange something in Utrecht. We could also do it in the ABC Treehouse next month.</div><div><br></div><div>regards,<br>Klaas<br><br><div class="gmail_quote">On Thu, Mar 25, 2010 at 10:05 AM, C.T. Matsumoto <span dir="ltr"><<a href="mailto:c.t.matsumoto@gmail.com">c.t.matsumoto@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello,<br>
<br>
Thanks for all the great talks last night at the PUN. It was a great time, even though a bit late.<br>
<br>
Last night I very shortly presented an idea to try out a Coder's Dojo at the ABC space. It was great to meet some other people who are interested and as well have already tried out their own Dojo.<br>
<br>
Here is the information I've found about a Dojo. After last night I know that there are different ways to run a Dojo, but this information has two types of Dojo, and rules, so it will be a good starting point that we can mix with other people's experience.<br>
<br>
For now we've got the space, and it looks like we've got the interest, but we haven't got a challenge, and if we try to hold this more often challenges.<br>
<br>
For me, I'd like to try a Randori style Dojo.<br>
<br>
Types of Dojo's<br>
--------------- <br>
<br>
<br>
<br>
<br>
There are two type of Coding Dojo meetings. The first is called Kata <br>
<br>
which is a rehearsed choreography of developing a solution for a given <br>
<br>
problem. For example someone presents a challenge of implementing a <br>
<br>
simple thread application. A member presents a solution in Java and <br>
<br>
proceeds to develop it during the session. She or he will have <br>
<br>
rehearsed the solution prior to the meeting, but will do all coding <br>
<br>
for the solution at the meeting. A previous solution is not imported <br>
<br>
into thesession and explained. The presenter actually creates the <br>
<br>
solution during the session. During the session, the group comments on <br>
<br>
the design and coding style and suggests changes to improve the <br>
<br>
solution. The session is very interactive and the group develops, with <br>
<br>
the presenter the solution they feel is the best, clearest, and <br>
<br>
simplest. There are breaks during the session for short design reviews <br>
<br>
where the group discusses the approach to solving the problem. <br>
<br>
<br>
<br>
<br>
The second style is called Randori which is an exploratory form of a <br>
<br>
kata where the whole group participates in carrying out an improvised <br>
<br>
choreography rather than following a rehearsed sequence of steps. Each <br>
<br>
member of the group takes a turn at the keyboard, adding to the <br>
<br>
code. For example, if there are six participants, each may have a <br>
<br>
seven minute turn as the developer. When the time is up, the co-pilot <br>
<br>
who was the other person in the pair programming team takes over as <br>
<br>
the pilot and a new co-pilot joins in. <br>
<br>
<br>
<br>
<br>
Rules of Dojo<br>
------------- <br>
<br>
<br>
<br>
<br>
The rules and sample session agenda presented here are preliminary and <br>
<br>
will be changed based on the experience gathered from previous <br>
<br>
sessions.<br>
<br>
* There is a coding challenge that is announced beforehand. <br>
<br>
<br>
<br>
<br>
* There is a room with one computer attached to video screen. <br>
<br>
<br>
<br>
<br>
* The presenter explains the coding challenge and starts the <br>
<br>
coding.The presenter may or may not choose to have a co-pilot. If <br>
<br>
this is a Randori session, a co-pilot is usually assigned so that <br>
<br>
when the switch occurs, the co-pilot takes over for the coder. <br>
<br>
<br>
<br>
<br>
* One half of the pair is changed every 5 minutes if the session is <br>
<br>
Randori. <br>
<br>
<br>
<br>
<br>
* The coder should continuously explain what she or he is doing. <br>
<br>
<br>
<br>
<br>
* The coder should stop when someone from the audience falls off the <br>
<br>
sled (has a question about understanding what the pair is doing) <br>
<br>
-- and only continue when that someone is back on track again. <br>
<br>
<br>
<br>
<br>
* All coders use TDD (Test-Driven Development). All produced code <br>
<br>
will be made publicly available using the Eclipse Common Public <br>
<br>
License. <br>
<br>
<br>
<br>
<br>
* The programming language to be used is announced in advance per <br>
<br>
session.<br>
<br>
(Coding Dojo <a href="http://web.cs.wpi.edu/~gpollice/Dojo.html#MeetingTime" target="_blank">http://web.cs.wpi.edu/~gpollice/Dojo.html#MeetingTime</a>)<br>
<br>
Cheers,<br>
<br>
Todd<br>
_______________________________________________<br>
Python-nl mailing list<br>
<a href="mailto:Python-nl@python.org" target="_blank">Python-nl@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-nl" target="_blank">http://mail.python.org/mailman/listinfo/python-nl</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.legalsense.nl">www.legalsense.nl</a><br>06 811 599 10<br>Skype: klaasvanschelven<br>
</div>