Timeline of the screencast
00:00 – 00:30: Install the CodersDojo-Client
00:30 – 01:45: Setup a kata with the CodersDojo-Client
01:45 – 10:20: Perform the prime factors kata (in Ruby)
10:20 – 12:09: Upload the kata to http://codersdojo.org and have a look at the statistics.

• Learn TDD: Walk through the steps of the featured katas and learn what the authors did in each step. After that try to do the kata the same way the author did. Upload the kata and compare with the choosen kata. Then improve!
• Improve by self reflection: Perform a kata with CodersDojo and upload it. Find out which moves could be improved by having a look at the longest moves and the moves with the most modifications (the statistics page will you tell). Analyse these moves with the review mode. Then improve!
• Improve by feedback of others: Perform a kata with CodersDojo and upload it. Send the link given at the statistics page to a friend or publish it (e.g. via Twitter) and ask for commenting the kata in the review mode. Then improve!
• Help others to improve: Review public katas and add comments. Tell the author that you commented his kata.
• Teach TDD: Perform a kata with CodersDojo and upload it. Explain your moves by commenting them in the review mode. Publish the kata link (e.g. through a blog or Twitter).
• More…: We think there are other useful use cases. If you found one please drop us a note: codersdojo@it-agile.de

Start with CodersDojo

Programmers improve their programming style in CodersDojo.

1. Most of the participants know what code katas are and doing code katas. But they focused on only few katas (nobody did more than 5 different katas).
2. A lot of people like to invest more time in code katas but don’t have the time. Most have to do code katas in their spare time and are not supported by their company.
3. For CodersDojo a lot of people want to see support of more programming languages and a better IDE. We are working on this.

Both Cyber-Dojo and CodersDojo are platforms for performing code katas. The systems aim at improving programming/TDD skills. With CodersDojo a programmer can record a kata performance and then get feedback from other programmers who are not at the same place at the same time. Cyber-Dojo is more a social event. Programmers sit together in front of one computer and perform code katas together. They can also do different katas in one dojo and play a mini-game besides. The feedback is generated by your team while performing a code kata.

Running Tested Features

Both systems are browser based applications. Users can edit code and run tests in their browsers. The result of the tests is shown after execution.

In Cyber-Dojo.com it is possible to sign in the same dojo with different computers. Users can see the test-status of the other users in the dojo. Programmers can choose between eight programming languages and thirteen code katas. After entering the dojo they get a short information about the aim of the chosen code kata. Users can divide their test and production code in several files. A little game can be played in a dojo. Programmers can ‘bank’ points for each kata with green tests. After a short period of time a bell rings as a reminder that the time has come to pass the keyboard to somebody else.

CodersDojo.com is designed to be used on one computer by a single user. CodersDojo supports Ruby as programming language. CodersDojo records all test executions. After finishing a code kata the user can see some statistical information about the code kata, e.g. a diagram of the red-green cycles. The user can browse the code kata to see all single steps of the code kata in chronological order. It is possible to sent the code kata to an other person via a generated link. This other person can comment every single step of the code kata to give feedback for improving the kata.

Suitability

CodersDojo.com is designed to perform a code kata and get feedback later. Users can decouple the work on the code kata and the feedback process. It is not necessary for somebody else to be there at the same time.

Cyber-Dojo.com shows its benefits when a group of people codes at the same time – in one place or or at different places. It is designed to support synchronous cooperation and may generate face-to-face feedback when a kata is performed as team. In case of working in different places it may be motivating to make an appointment and work on a code kata.