magpiebrain

After some service hick-ups Gradwell hae got things back to normal. Despite their main file server being down for two days, the worst disruption I faced was the blog being unavailable for a couple of hours, then it being in a read only state for an hour or so.

My otherwise excellent ISP Gradwell suffered a heart stopping (for me at least) outage today:

Our primary fileserver has failed, causing primarily an outage of out web and shell account services. We are working on recovering this machine as quickly as possible, and apologise for the inconvenience this will cause. We regret no ETA is currently available.

I was at work an unable to check the dates of my last backups, but its seems to be back and working now. The outage was reported at 8am and fixed by 10:30am so no harm done. I am however going to make sure I have everything backed up when I get home tonight!

I’ve been interested in XP for a while now. Whilst many of the rules outlined in XP have always made perfect sense to me (simple design, frequent unit testing), the one that really made me sceptical was the notion of “Pair Programming(Extreme Rules – Pair Programming)”:http://www.extremeprogramming.org/rules/pair.html, which forms much of the focus of a recent “Wired article(Wired – The New X-Men)”:http://www.wired.com/wired/archive/11.09/xmen.html?pg=1&topic=&topic_set=. For the uninitiated, pair programming has two programmers working at the same desk – one programmer ‘drives’ whilst the other watches. The idea is that they can bounce ideas of each other, and while the coder doing the actual typing can be quite focused on a single line, the other can pick up simple mistakes such as missing semi-colons and the like. The net result is that despite the apparent upfront loss in productivity bugs occur less frequently, and when they do appear they are fixed more quickly.

Although the practice adds 15 percent per programmer to the time it takes to complete a task, the lost productivity is offset by having fewer bugs to fix. “Pre-XP,” says Kevin Yu, “an eight-hour debugging session wasn’t unusual. With XP we spend about half an hour.” Meanwhile, 90 percent of the 41 coders in the study enjoyed working together more than alone, and almost all were “more confident in their solutions.”

My main reservation concerning Pair Programming is the issue of finding someone compatible to work with – I often find it frustrating to try and explain my ideas to people who take longer to understand the concepts being discussed than I do. Likewise trying to reign the enthusiasm of a colleague who completely understands how their one line obfuscated beyond all recognition Perl script works long enough to work out whats going on can really make a dent in my patience. That said maybe I should follow Kent Beck’s (the father of XP programming) advice:

“Extreme programming is an emotional experience,” he maintains. “When you feel it, you understand.” Then he adds a typically cheeky metaphor. “Talking about XP and trying it are two different things – like reading The Joy of Sex versus losing your virginity.”

Perhaps when it comes to looking for my next job XP should be on my “would like to have” list along with reasonable working hours, time for training and decent pay!