Wednesday, September 26, 2007

Incoming bestsellers

After a dinner with Chris and Miquel we ended up with a bunch of titles for potential bestsellers.

  • Binge Coding, when too much is just enough
  • Glamour Programming (ok …I am recycling here…)
  • Beer Driven Development
  • Unintentional Programming, Oh bollocks!
  • The Dogmatic Programmer, It's my way or the highway, buddy!

I took pictures of the potential covers, but lame camera, low light and a straight firm hand made them definitely not worth publishing. Let's see if I can come up with something better with a drawing tool…

Pair programming’s side effects

While attending JAOO 2007 I had the chance to talk for a while with Pramod Sadalage, which gave me some interesting hints about pair programming. I was basically concerned about the amount of time spent by development teams with Instant Messaging tools, such as Skype, ICQ, GoogleTalk. There's basically nothing wrong with those tools; normally they're something that acts as a development process accelerator, especially in offshore or de-localized development situations. Unfortunately, this is not always true: instant messaging can be easily abused, and cause frequent interruptions in people's work. The number of interruptions is related to the team size, but has something to do with the way tasks are assigned to people, with the underlying architecture, which increase the number of people you are depending upon to complete your task, assuming that all the incoming messages are related to the job … which is basically not true. Given that every interruption destroy concentration in the receiver and that it takes about 15 minutes to become productive away, preserving the so-called state of flow is a crucial task.

Pramod's suggestion was to adopt pair programming, on a dedicate workstation. When you're pairing you are less inclined to chat with others, because your peer is just sitting there. The dedicate workstation also helps, because you can configure it not to have IM software installed on it. Pairing sessions anyway aren't for the whole day. So after a couple of hours – and with a bunch of well done lines of code – developers can check out the e-mail, and so on. But productive time is preserved.

Tags: , ,