It’s no secret that’s I’m a fan of code katas. Over the years I’ve spent quite a bit of time on CodeWars and other kata platforms, and I’ve written a large handful of Literate Commit style articles outlining kata solutions:
I’m a huge fan of the idea behind code katas, and I believe they provide valuable exercise for your programming muscles.
We Should be Training
That being said, the common form of code kata is just that: exercise. Something to get your heart pumping and your muscles moving, but devoid of any real goal.
Exercise is physical activity for its own sake, a workout done for the effect it produces today, during the workout or right after you’re through.
Does my career benefit from reimplementing search algorithms? Probably not. How much do my clients benefit from my skill at coming up with clever solutions to contrived puzzles? Resoundingly little. What’s the objective value of being able to write a non-recursive fibonacci sequence generator? Zero dollars.
Instead of exercising, we should be training.
Our focused practice time should be structured around and focused towards a particular goal. To make the most of our time, this goal should be practical and valuable.
Training is physical activity done with a longer-term goal in mind, the constituent workouts of which are specifically designed to produce that goal.
We should be working towards mastery of skills that bring value to ourselves and those around us.
Practical Code Katas
Lately I’ve been working on what I call “practical code katas”; katas designed to objectively improve my skills as a working, professional web developer.
The first kata I’ve been practicing is fairly simple. Here it is:
Build a web application that lets new users register using a username and a password, and that lets existing users log in and log out. Protect at least one route in the application from unauthenticated users.
The rules for practicing this kata are simple: you can do whatever you want.
You can use any languages you want. You can use any frameworks you want. You can use any tools you want. Nothing is off limits, as long as you correctly, securely, and honestly complete the kata as described.
I encourage you to go try the kata!
How long did it take you? Are you satisfied with the result? Are you satisfied with your process? Where did you get stuck? What did you have to look up? Where can you improve?
When I first completed this practical code kata, I was following along with the first several chapters in the excellent Programming Phoenix book (affiliate link) by Chris McCord, Bruce Tate, and José Valim. Copying nearly every example verbatim (and trying to convert to a Phoenix 1.3 style) as I read and followed along, it took me roughly four hours to first complete the kata.
Later, I tried practicing the kata again. This time, I had a rough lay of the land, and I knew vaguely how to accomplish the task. Two hours and many references back to Programming Phoenix later, I finished the kata.
And then I did it again. This time it only took me forty five minutes. I found myself stumbling on a few pieces of trivia (“Where does
assign live? Oh right,
Plug.Conn…”), but the process went much more smoothly than before.
And I did it again. Now I was down to thirty minutes. I still found myself forgetting small details (remember:
*_path helpers live in
So I did it again, and again, and again…
The Benefits of Training
As I continue intentionally practicing with this kata and others like it, I continue to find more and more benefits. Some benefits are obvious, while others are more subtle.
An obvious benefit of this type of routine, intentional practice of a small set of common tasks is that implementing those tasks in a real-world project becomes as natural as breathing. Even better, if I ever need to implement a task similar to any of my katas, I’ll immediately know where to start and what to change.
Repetition breeds familiarity.
Familiarity breeds confidence.
Confidence breeds success.
Practicing this type of kata has not only improved my ability to know what code I need to write, but also my ability to write it.
As I repeatedly find myself writing and rewriting identical sections of code time after time, I start looking for shortcuts. I start to notice places where I can use new Vim tricks I’ve been trying to learn. I build up my snippet library with generic, repeated blocks of code. I get more comfortable with the nuts and bolts of what I do for a living: writing code.
If it wasn’t obvious before, it’s probably obvious now. I love code katas.
That being said, I think we haven’t been using code katas up to their full potential. Intentional, repeated practice of a set of practical, real-world problems can help us greatly improve our skills as professional web developers.
Stop exercising, and start training!