Code Katas: Practicing Your Craft

Editor's Notes

• #3 Verbs vs. NounsRequirements“Plans are useless, but planning is invaluable” – Dwight D. Eisenhowerthe value is the process that everyone goes through in order to produce the document: the understanding gained, the relationships forged, the negotiations, the compromises, and all the other little interactions which share information.QualityPlan, measure, build a quality product!Quality is PART OF THE PROCESS. Quality is in the spirit of the smallest of our daily activities.
• #4 Read quote
• #5 Who plays a musical instrument? Practice time vs. performance time?ScalesArpeggiosExtended tones (wind instruments)Various technical patternsLast bars of Franz Liszt's Transcendental Étude No. 2: one of the most difficult of Liszt's études, this is a study in passages for alternating and overlapping hands.Sports is the same way, how much time is spent practicing versus performing?
• #6 Clearly each of you is here at Code Camp on a Saturday because you KNOW that you can’t get everything you need for your profession, to be a master of your craft by practicing “on the job”.
• #8 Provide a temporal oasis where it’s OK not to worry about some approaching deadline.Learn how to play with code: how to make mistakes, how to improvise, how to reflect, and how to measure. This is hard: we’re trained to try to do things right rather than improvise.These “keys” are fundamentally incompatible with “on the job” learning.One the job has deadlines and restrictions. It’s very visible to other people so mistakes are less tolerated.Sure there is a component to this. We can learn on the job. “Live” experience is important. For example with public speaking, you can practice and practice, but actually presenting is different. Practicing helps, but it doesn’t replace real experience.SportsMusicMilitary combatCooking for your in-laws
• #9 The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality. His procedure was simple: on the final day of class he would bring in his bathroom scales and weigh the work of the "quantity" group: fifty pound of pots rated an "A", forty pounds a "B", and so on. Those being graded on "quality", however, needed to produce only one pot - albeit a perfect one - to get an "A".Well, came grading time and a curious fact emerged: the works of highest quality were all produced by the group being graded for quantity. It seems that while the "quantity" group was busily churning out piles of work - and learning from their mistakes - the "quality" group had sat theorizing about perfection, and in the end had little more to show for their efforts than grandiose theories and a pile of dead clay.http://www.codinghorror.com/blog/2008/08/quantity-always-trumps-quality.htmlArt & Fear: Observations On the Perils (and Rewards) of Artmaking [Paperback]David Bayles (Author), Ted Orland (Author)We learn by DOING!I would argue that we can’t do quantity on the job. We have to get the volume of repetitions elsewhere.
• #10 Concept introduced to software by Alistair CockburnShu - the technical foundation of the artSingle instructorCopy techniques without modificationit is the instructor that decides when the student moves on from Shu to Ha, not the studentIt’s up to the student to follow the instructor’s teaching as an empty vessel to be filled upHareflect on the meaning and purpose of everything that s/he has learned and thus come to a deeper understanding of the artRimust think originally and develop from background knowledge original thoughts about the art and test them against the reality of his or her background knowledge and conclusions as well as the demands of everyday lifethe art truly becomes the practitioner’s own and to some extent his or her own creationInvent own techniques
• #11 Everyone is at different levels with different skills that they are developing, but nobody is master of all skills.We often jump right into critiquing a method or idea instead of attempting it “as is” first. We think that we’re so smart that we can skip past the “beginner” stuff and get right into it.Programmers are especially susceptible to this as we have sizable egos generally.Seek first to understand.
• #12 Slow down!Practice the feel and to internalize the movesBuilding muscle memoryChange your intuitionTrain your eyes and fingers to recognize and respond to patternsValue in repetition even if you don’t agree.You may not like what the kata is teaching you, but that is learning too.
• #13 Japanese word describing detailed choreographed patterns of movements practiced either solo or in pairs.A kata is a coding exercise that performed repeatedly and perfected.Framework for focused practiceTDD/Unit TestsPerformanceStructureMemory UseTool use (IDE, text editor)Practice comes to an end; with a real problem… not so muchPath is laid out for you so there is a definite end
• #15 Group is given a problem.Time box – you have x amount of time per pairPing Pong – one person writes a test, next codes to green and writes next test, next codes to green and writes test…
• #17 Anybody attended one of these?Working to have one in Utah.
• #18 As we learned earlier, the best way to learn is by experimenting and repeating so that’s what we’re going to do
• #19 Remember that the problem that we solved today is not really that important. It’s not important that we have a piece of code to score a bowling game. It is important that we go through the exercise and take from it what we can.