Category Archives: Methodologies

Methodologies

Software Craftsmanship week: A brief history

To conclude the software craftsmanship week, I would like to take a brief look on the history of this movement. So, we’ll take a look on the Software Craftsmanship book, on the creation of the Manifesto for Software Craftsmanship, on the writing of the Software Craftsman’s Ethic, The Wandering Book and some apprentice blogs, some conferences, and the software craftsman swap programs from Obtiva, 8thLight, and Relevance. WikiPedia also has a great history on it with some points I won’t mention here.

Continue reading Software Craftsmanship week: A brief history

Software Craftsmanship week: Deliberate Practice and Learning

Reflecting over the history of the Manifesto for Software Craftsmanship and the ideas we concluded for the The Software Craftsman’s Ethic, so far I just covered two aspects. The key ideas behind the manifesto and the ethic statements is that craftsman care for their work, taking pride in it, they practice their craft regularly, they learn deliberately, and finally they share their knowledge in communities and with peers. So far, we have started our journey this week with on the sharing part, and continued to take a closer look on the caring part in the last two days. Today, we will spent time on deliberate practice and learning parts.

Continue reading Software Craftsmanship week: Deliberate Practice and Learning

Software Craftsmanship week: Clean Tests

To some degree I envy programmers for their clear guidelines. One of these set of these guidelines is well-written in Robert Martin’s book Clean Code – A Handbook of Agile Software Craftsmanship. (Personally, I hope that Kurt Häusler will review it this Software Craftsmanship week on his blog.) So, today I decided to write about Clean Tests, and what a book on the topic should cover.

Continue reading Software Craftsmanship week: Clean Tests

Software Craftsmanship week: Apprenticeship in Software Testing

The Mis-education and Re-education of a software tester is a topic that I see discussed heavily. In the past I have reflected back about my personal education as a software tester, and what I had to contribute myself to this. After having read Pete McBreen’s Software Craftsmanship – The New Imperative I started to understand part of the problem. In chapter 2 McBreen explains most flaws of the Software Engineering metaphor. This is my first blog post in the Software Craftsmanship week 2010. I will spend some thoughts on related topics over the course of the whole week. Today, I would like to take a closer look on educational models for testers – in Software Engineering and what clever people have come up with for compensation.

Continue reading Software Craftsmanship week: Apprenticeship in Software Testing

The challenge of the Nine Smurfs

On Monday, I issued a little challenge on a smurf house we got as a wedding gift. The challenge resulted in eight comments overall, and I was struggling to clarify my initial observation. To make things short, I learned something from the comments. What I initially observed was, that the Brainy Smurf was reading in front of a flower, while Smurfette carried a watering pot in front of a pile of books on the first floor on the left. From the comments on my blog I learned, that I should have taken the hindsight, and do some more follow-up testing. The variety of similar mistakes in the arrangement of the smurfs was fabulous.

That said, when going through the comments, I need to find a way to rank the responses I got. A simple second-order measurement could be the number of comments per individual. In this category, Jeroen Rosink is the clear winner. He left two comments. This does not say anything regarding the quality of the comments, of course. So, I needed to find a different rating scheme.

So, on the contextual things remarked, I even didn’t get a hint, why Painter Smurf is in front of the cake, why Handy Smurf is trying to fix the gift in front of him, why Chef Smurf wants to taste the blue paint, or what any of the other smurfs do there.

Regarding the building, the inconsistencies in the building itself and the weather outside are great things to notice. In addition the arrangement of the Smurfs with regards to the background could be a point. Why is Papa Smurf working in that distance to his table? Why does the Fisher Smurf fish the pillow from the Sleepy? Where are the stairs to the first floor? Where is the chimney outside? Well, if you would be able to look on the back of the house (a mushroom) and get a 3d impression, you could see that the walls on the first floor are less in depth than on the ground. So, the chimney could go out of the mushroom house outside, but on the back of the house no indication of any chimney are present. The comment from ElizaF was also very well put. The structure of the building is not well architectured, as there is no kitchen, and no toilets. Maybe Smurfs don’t need them.

Finally, the answer I liked best came from Anne-Marie Charrett, and I was tempted to state that it’s a pure example of the English humor, but recognizing that she’s from Ireland, I realized that I should refuse.

I dunno, if you live in a world where its ok to have blue skin, anything could be acceptable. :)

Well said, Anne-Marie.

Last, but not least, here are some things I missed. I didn’t see anyone trying to find references on the Smurfs and the particular campaign run by a German producer. Before putting up the challenge, I needed to verify that our Smurfs weren’t just misaligned. Thereby I found a picture of the arrangements as well as a selling offer for the diorama. For this write-up I used the list of Smurfs from wikipedia. The plug Milk, minus Kakao is part of the brand Kinder Überraschung, indicating that these sweet chocolate eggs are some kind of healthy. Overall this is very great domain knowledge, which could have helped in the decision on “problem or not a problem?”

Craftsmanship and Quality

Currently there is a thread ongoing on the XP mailing list. Based on a rant from Nick Robinson, the discussion started about programmers that take pride in their work as opposed to programmers that just do that coding stuff. Today, Kurt Häusler wrote a reply in which he states his experience. You should go and read it – now – the initial rant from Robinson is in there, too. I’ll wait here for you to come back.

Continue reading Craftsmanship and Quality

Testing Dojos

About a year ago, I heard about Coding Dojos for the first time. Getting back to work, I nearly immediately tried out the idea with some colleagues. The implementation was great, and we had a lot of fun. Every since I wondered how to get testers involved into this deliberate learning. It took me some time and thought, but now I ended up with Testing Dojos. We ran several of them at work so far. I decided to provide you with some know-how that should get you started as well. In case you’re looking for personal experience, I will be presenting the topic together with a sample session at the XP 2010 conference in Trondheim in June this year.

Continue reading Testing Dojos