That is an interesting take. I suppose I would agree that katas would help you build a base that allows you to run on autopilot when performing certain tasks. The main problem I have is when katas are practiced beyond that point instead of a new challenge.

I do test drive. And I do think it is a design activity. It definitely makes sense to use katas for learning in that way.

Spot on!

John (OP), do you test drive? Do you view test-driving as a design activity?

That’s what katas are about. We perform katas until test-driving a given design cleanly and efficiently becomes second nature, until the red, green, refactor motions for a given context become second nature. This enables us to move beyond mechanics and focus on the larger picture. If you are focused on code that satisfies a solution rather than on how you create that code (aka “doing it wrong”), katas won’t benefit you much.

I agree with you that katas that are varied and not repeated do not fit the definition. These have their importance in developing problem solving skills but, to continue the martial arts analogy, are more akin to sparring bouts. It’s disappointing that people don’t practice katas more — people should learn to walk well before they expand into Parkour.

Solving the same problem over and over again does not equate to obtaining the same answers. You presume that katas are purely mechanical, but I have seen my code improve by doing precisely that. “Blind following” is foolish — and in fact, it is not really done in practice. Watching a kata executed by another, and then attacking it rarely results in the same solution and the same way.

As to your thesis dissing katas, I will have to join those who demur. In particular, when teaching test-first development, I have found kata practice a terrific vehicle for adopting the non-intuitive disciplines that are triangulation and strategic generalization. Learning to take small steps is a very difficult discipline, particularly for the smartest and most intuitive cowboys. Learning to develop with discipline and to go slow, and that by doing so, you end up going much, much faster and more reliably. With your insights into simplifying code, I found your remarks confusing.

It is also an excellent way to learn to pair — to develop a rhythm with a pairing team, and to build parity with a new partner.

For my part, I have found that repeating katas has often led me to new insights to old problems. Additionally, it facilitates developing a muscle memory that allows mechanical disciplines that are essential in some aspects of a->b problem solving go quickly, without the frustrations of refraining from skipped steps, “knowing” how to get there from here.

At least for many agile practices, kata practice is an excellent way to learn, and achieve a degree of mastery. There will always be a place for intuition and problem solving, of course, but the technique is also key. And kata practice is the best way I have seen to develop those techniques.

To address what you said about creating 180 web sites: there is a large amount of value in seeing lots of different problems and working on many different things over a long period of time. Focused practice on a single thing is valuable, but I have found that you learn much more and gain much wider perspectives from doing things that have a wide berth rather than focused activities. I do agree that both are necessary though.

Code Katas used correctly are good, used incorrectly in the same way someone would practice for a sport or to play guitar for instance, they tend to be a waste of time.

Why would you ever hire Jennifer who made 180 websites in 180 days? if you don’t need a person who can generate a lot of websites in a short time period(I hope the websites are all different 🙂 ). I’d never hire Jennifer for anything else than generating as many websites in as short time as possible. Creating 180 websites seems like a dumb enough exercise to stop me from hiring this person.

Code Kata is an exercise which is useful for improving your programming skills in certain ways. It shouldn’t be confused with learning programming from scratch or as the “only tool to learn and improve your programming skills”. It’s one tool of many to help you practice and develop your skills. I’m sure Jennifer would be an even better programmer if she created 25 well-designed web sites and performed 10 different Code Katas in 180 days in stead of doing the same code kata for 180 days or creating 180 different websites just for the sake of it.

Thanks Cory, because of your input, I went ahead and updated this post to point to this comment chain at the top and also I reworded the definition of code kata to say that some people think code katas are… instead of making a large generalization. Appreciate your input here. 🙂