Performing Code Katas

The post describes katas as a discipline that helps software craftspeople build muscle memory, practice logical thought, and try familiar ideas from a different angle. At 8th Light, kata work can be a warm-up before the day’s work or a way to regain clarity on a hard problem, and polished katas may be performed live for peers as entertainment.

Reading notes

#

• Katas are presented as a practice for preserving and refining skills through repetition.
• In software, they are used to build muscle memory, exercise reasoning, and approach familiar ideas differently.
• 8th Light treats katas as part of craftsmanship, and Mike Ebert uses them to warm up or regain clarity.
• A kata performance is described as entertainment, not as a test of mastery.
• The suggested length is five to ten minutes, with seven or more minutes seen as more realistic.
• Performances should begin and end with an introduction and a closing that states the performer’s name and kata.
• A large font, minimal scrolling, and a quick projector check are recommended.
• White background with black text is preferred, and a custom presentation theme can reduce distractions.
• Fast typing matters, but accuracy still matters, and copy-paste should be avoided during the performance.
• Keyboard shortcuts should replace mouse use whenever possible.
• Each kata should have one clear theme that gives the audience a small lesson to take away.
• The performer should keep code, tests, and test runs visible at all times.
• A kata can start from scratch or from an existing codebase.
• The performer must choose between speaking, music, or silence, with each option used intentionally.
• The author says technique should be flawless, especially when using test-driven design or a new language.
• The post uses Sandro Padin’s Fizzbuzz kata in Clojure as an example of theme and music working together.
• The closing compares kata performances to songs and says the goal is to raise standards and encourage performances worth remembering.