Hmmm... It's a couple of thousand lines of code I think. I forget. If you go to the link, the code is there (I run everything through Github). Each pomodoro

Hmmm... It's a couple of thousand lines of code I think. I forget. If you go to the link, the code is there (I run everything through Github). Each pomodoro is in it's own branch and I kept them around so that I could study the diffs later (haven't gotten around to it yet). My original goal was to practice constant refactoring on a non-toy sized problem. Normal katas necessarily require you to work on toy problems. Because of this many interesting real world problems never come up. Frequently you can see people using techniques that aren't sustainable, for instance. In the end, while I did get some value from that, by far the most interesting thing I discovered was that you can write code 1 pomodoro a day! If you take this as being about 1 weeks worth of work, I think my productivity is a bit lower than normal. However, it's not off by that much. Even more interestingly, because I work in a timezone 9 hours separated from my colleagues I've always wanted to be able to hand over work. In other words, 2 people working on the same story. 1 person works during the night and the other person works during the day. They hand over the code in the morning and the evening. Using the TODO list techniques I was using in the kata (and making sure to end the day on a failing test), I've actually been able to accomplish this with like minded colleagues. It's actually quite incredible. Probably I should write a blog post about it ;-)