// August 3rd, 2012 // No Comments » // Agile, Tools
Code Katas are so useful we wanted to analyze, share, and relive the infamous experience. Code katas are a core training practice for software development that I believe heavily in. To read more about what they are and a list of good ones to practice see my Dojo Code Katas post. Here I want to discuss a script I have been working on to relive the kata step by step.
How We Got Here
We have been doing monthly Randoris at work and we have been including committing to mercurial as part of our practice. Every refactor and every test/passing code pair we commit. This helps us practice committing often, a key rule to distributed version control, and writing better commit messages. This also allows us to relive the commits of each step/person as we rotate through the group. But there was no way to take those commits/diffs and output a useful report to quickly relive it.
What We Wanted
We wanted to be able to post the output back to our confluence wiki for a few reason. We wanted to be able to analyze where we went right and where we went wrong. We wanted others who couldn’t participate to be able to relive it as if they were there. We wanted different teams to be able to see how the same problem is solved by each other and note the subtle differences everyone has and some tricks that certain teams do vs others. Who knows of all the great possibilities, but an open source code kata repo wasn’t good enough. It had to be fast to view, easy to get to, and easy to analyze.