Raging Against the Machines
This is less an apology than an explanation.
The lightness of posting last week reflected my being very busy. Pleasantly busy - although I still haven't seen half of the people I was looking forward to seeing when I got back to London, I have managed to see a number of important people individually, which has the advantage that we can catch up much more meaningfully, but the drawback of taking a lot of time while there are still too many of people I haven't met up with at all.
This week has been different. The weekend felt a little more like normality, so I started the week with very good intentions of spending the days in some sense at work, and going out a couple of evenings but also spending some time with my parents, and making time to make some long chatty phone calls to people outside London. I haven't been very successful because a large share of my time, and an even larger share of my energy have been eaten up by trying to get a wireless network up and running in the house. It ought to be so easy....
I won't go into the technical details of what's going wrong, but there are two reasons why this is driving me much more mad than technical troubles usually do. On the one hand there is my almost boundless enthusiasm for what this technology will make possible, when it is accessible to people who don't have several days to spare getting it running and a large base of computer knowledge to draw on (more on this in a subsequent post once I have it working and can write in my room). On the other is the manner of the troubles. If I am stuck with something that simply doesn't work, but responds systematically to changes in my approach, I get frustrated but ultimately I can deal with it. In this instance, I have several times
thought I had the network fixed, gone and made myself a cup of tea (not just any old tea; more on
that later too), started to use the network (and it is great when the damn thing works), and then something has gone wrong. I can usually see what the trigger was - it tends to be one or other of the computers being rebooted - but I have as yet to work out what changes in this situation, and how to put it right. In practical terms it means that each time it fails I have to waste an unpredictable (and usually considerable) amount of time tinkering aimlessly until it miraculously works again. Emotionally it's how I imagine working with very young children to be like - no matter how hard I try these machines just don't respond predictably or do what I want them to.