RSS Feed

Latest Entries

First time here?


Kevlin Henney – 3 things every programmer should know

During the ACCU 2010 conference in London, I got to get on audio, several of the interesting people who attended and spoke at the conference.

One of them was Kevlin Henney. I first got to see him speaking during NDC 2009 in Norway. He was fascinating in the way he approached sophisticated architecture topics, and his lively and funny way of making everything more understandable.

Kevlin is also the main character behind the book 97 things every developer should know and several other books.

In this 20 minute audio mp3, we start off with a simple question: what are the three things every programmer should know? (you can watch Kevlin on this years NDC in Norway as well. I highly recommend it! (he’s also on twitter)

Download the mp3 – 20 min.


Interview: Patrick Kua : Agile Coach

This time, I talk with Patrick Kua, an Agile Coach living in the UK, about various subjects. Among them – the various types of tests, what is “Done”?, The difference between Team Leader and Team Manager and more.

Download mp3 – 29 minutes.



Interview: James Bach – The role of the tester

During the ACCU conference in London (at which I am still stuck due to the ash cloud while writing this), I got to speak with many interesting people, and even recorded some of those conversations.

One of the talks I enjoyed the most was with Tester James Bach, who gave a thrilling keynote about the role of the tester in the organization, and the idea of exploratory testing.

In this recording I talk to James about what real testers need to be, how to interview a tester for a job, the idea of exploratory testing, automated checks vs. manual, sapient  tests and many other things.

James has taken a clear leadership role in changing the perceptions many of us have about what testers are and should be, and what testing should be like.

Download mp3 - full time is 75 minutes.



James really made me change some of my points of view about what and where we might need testers, and how unit testing and “sapient" testing” go together, and don’t cancel each other out.


Move-Around kata for team leaders

Here’s an experiment for software team leaders: a set of katas (things you repeat exactly the same way many times).

Let’s try to do the following kata once a day:


  1. Get out of your chair and lock your computer
  2. For each team mate that sits in your floor:
    1. Ask “can you show me what you are you working on?”
    2. See at least one technical document they wrote (source code, documentation, build script..)
    3. If you think they could have done a better job, challenge them to find a better way to do the job without giving them the whole answer
    4. This should take no more than 5-10 minutes per team mate but you can take longer if you like.

What other katas do you recommend?


my worst team leaders

my worst team leaders

  • Didn’t bother to check or see if I was stuck on something
  • Didn’t coach me or teach me to be a better developer or team mate
  • Didn’t earn my trust in their technical skills
  • Didn’t have a problem with anything I was doing (good or bad)
  • Spent most of their time away from me
  • Smiled a lot, but didn’t say too much
  • were really nice
  • did not take care of any impediments I presented
  • did not challenge me