Slide 2
Slide 2 text
As can be seen on the next slide, in late 2000 Uncle Bob (Robert Martin) and Bob Koss pair programmed (in a hotel room) the Bowling Game, and (two years later) the ensuing
programming episode was captured in glorious detail in the fourty or so pages constituting chapter six of the book Agile Software Development, Principles, Patterns, and Practices.
The two Bobs were both associated members of Object Mentor, a now defunct company which was founded by Uncle Bob in 1991, and which advocated object-oriented software
technologies and cutting-edge Agile development methodologies. In 1998, Object Mentor helped to define the Agile development method known as Extreme Programming. In 2000,
Object Mentor helped form the Agile Alliance โ a group of professionals dedicated to the advocacy of lean and emergent software methods.
By 2005 Uncle Bob had practised the Bowling Game code kata hundreds of times (see slide after next for an overview of the term code kata), and although one of the key aspects of a
code kata is that most times (if not each time) we โdoโ a particular kata, we go through a unique learning experience, he decided to capture, in a deck called Bowling Game Kata, an
example of the sequence of TDD steps that one may go through when performing the kata (see subsequent slides for where to find the original deck). The sequence illustrated in the
deck is not meant to be โtheโ ideal sequence, or a typical sequence. It is just a sequence whose length and particulars make it both amenable to capturing in a deck, and didactically
suitable as a demonstration of โdoingโ that kata.
Here is what we are going to do in this deck (it will become perfectly obvious once we actually do it, so donโt worry if you find some or all of the following unclear):
โข Fire up coding tool Claude Code
โข Go through the original Bowling Game Kata deck, one slide at a time, and do the following for each original slide:
โข Show a copy of the original slide that has been modified as described in the next two bullet points
โข If relevant, highlight the code that is being added and/or modified in the TDD step illustrated by the original slide
โข Add a slide number
โข Add a slide showing:
โข how the code in the current original slide differs from the code in the previous original slide
โข a command that causes Claude to make code changes that result in the above differences
โข Add one or more slides showing an interaction in which we issue Claude with the command, and Claude obeys it, keeping us informed of actions taken, and their outcome.
@philip_schwarz
โข Original slides are going to be marked with these two icons and a with page number
โข Highlighted code in original slides will look like this
โข Modified code in original slides will look like this
โข The Claude commands that weโll be issuing will look like this
run the test suite
green
11
orange