So I’m sitting here at SCNA, and it’s great to talk about improving our craftsmanship, but what are we doing about it? And I’m very struck by what Keavy says about artists having a culture of critical review, which we totally don’t have. So I talk to Max, and I say, “We’ve got all the right people in the room, but we’re not pushing the state of the art forward!” And I whine about the state of programming education, and how we don’t have the culture of critique, and all that, and he says, “We need a fully worked example that we can all stand behind, like a Kata, but for a full size problem.”
So, that’s what we’re going to do. Thirty days of development, with review and commentary on the code at each step, hopefully tracking real changes to requirements and being a full sized app. We want reviews of the code at each step, and as much feedback as we can get. Once we get the thing “complete”, We should build a finished “episode” with code, commentary, and reviews. Ultimately, We’d like something that someone can read and get a good example of how software craftsmen work and do a full sized project.
We have a twitter hashtag: #fullsizekata
Questions: What is the best way to foster consensus on each iteration?