"There are no limits. There are only plateaus, and you must not stay there, you must go beyond them."
~Bruce Lee

• You can't write any production code until you have first written a failing unit test.
• You can't write more of a unit test than is sufficient to fail, and not compiling is failing.
• You can't write more production code than is sufficient to pass the currently failing unit test.

Adhere to them in your kata.

You'll be surprised to learn how others have test driven something. Or of struggles they've had in doing so. Learn from their experiences and openly share yours.

One of my favorite leadership principles is "Know yourself and seek self improvement". Take time at the end of the kata to know yourself better so that you can improve and therefore help others improve.

Right now, we're trying to tackle a new Kata each week. Each directory in here corresponds to one of these katas. If you'd like to work through this weeks kata, checkout this repository and create a subdirectory under the kata that corresponds to your github handle. For example, if I wanted to work on the 'data-munging' kata, I'd add a directory ./data-munging/daveshah and if I wanted to work on the 'adder' kata, I'd create ./adder/daveshah. If you take a look at some of these, you can get an idea of what folks have done.

If you have any problems, feel free to open up a Github issue or, for quicker feedback, post something here: .

Feel free to comment on code others have commited as well! Again, the goal of this is learning and getting feedback from others always helps!