Things that go Bang in the Night

So, two of the more controversial events in the calendar have passed for another year – Halloween and Bonfire Night.

They are of course controversial for very different reasons. Halloween, which was a week ago causes much discussion in the media due to the fears caused by trick or treating, more particularly with older young people throwing eggs, resulting in bans on the sale of eggs. For a number of years our area has operated a policy of trying to discourage teenagers from trick or treating at all, and this year publicised a zero tollerance policy towards egg throwing. According to our local paper, Police attended five incidents of trick or treaters throwing eggs, and one of a pensioner throwing an egg at trick or treaters! This perhaps indicates that high profile stories result in a percieved fear is a lot worse than the actual occurences.

The controversy over Bonfire Night is very different, and after the events this weekend in Northamptonshire focusing much more on safety. For many years campaigners have been encouraging people to attend big displays, but as events this weekend show, even the most professional of these still can have accidents. Indeed a friend at work attended a local display where people in the crowd were hit by stray fireworks, despite the crowd being kept the required distance from the display. Having said that the number of injuries at private parties is still significantly more, with the 2004 figures making grim reading, with 590 of the 1160 injuries occuring at home or private parties compared to 161 at public displays. Even more worrying is that 368 of the 1160 injuries were to those under 13. However it is worth noting that the second largest group of accidents is 317 injuries in the street, from firework misuse such as this recent case in Wales.

So, do I think that next year will be any different? Somehow I doubt it. Halloween is still fairly minor compared to North America, however many areas of the country are, like our area, trying the twin approach of encouraging Halloween parties whilst operating a zero tollerance policy towards troublemakers. Certainly the perception of trouble seems to be worse.

As to Bonfire Night, the actual reason for the celebration, marking the thwarting of an attempt to blow up the British Parliament has largely been forgotten. However the present day British Parliament has recently backed a tightening of the rules, however with every case such as the 11 year old in Wales there are calls for a total ban on sales to the general public. Perhaps it is slightly inconsistent that in a country like the UK with some of the tightest gun laws, and many other strong health and safety related laws, and despite the selection of accidents from this year any adult member of the general public can still purchase fireworks.

Cat Communication

Sophie 1

Reading Wil Shipley’s blog today it seems that his cats have been taking lessons from Sophie over making a fuss.

This morning, the word on the street (where the street is actually the foot of my bed) was that, sometime late last night, the cat food bowl ran almost empty.

This news was imparted to me with such urgency that I assumed it must have been meant for a much wider distribution, as if my fuzzy friends had used their super-keen senses to detect an imminent earthquake or another global-warming-induced hurricane.

It is well-known, of course, that cats can die to death from not eating for six hours. Or, in this case, from having to eat the kibble bits left on the bottom of the bowl, which is clearly less desirable, else why would it be left over? It was the kibble found wanting, and to have to eat it would be tantamount to death, at least.

We’re having a similar problem with Sophie at the moment. Like a lot of pets she is very much a creature of habit, and will start to get quite vocal if she doesn’t get fed at her usual times, don’t do things the way we usually do (for example when we go on holiday). On a usual day she expects food at about 6am, goes off and goes to sleep when we would usually leave for work, is sat on the stairs or behind the door when we get home, and in the evening it is demanding food for around 10pm.

However, this past week we have had the annual problem caused by the clock change, which of course she doesn’t cope with at all, so she’s decided that if we haven’t got up and fed her at 5am that we should be and she starts complaining. In the evening from about 7:30pm now she is trying to trip you up if you go anywhere near the kitchen, I assume on the basis that since we forgot to feed her until an hour later the night before, we need to be reminded early. In general we’re getting a lot of complaining because we’ve changed our schedule.

Matters are made somewhat worse by the fact that we’ve recently been shutting her out of our room at night, since she took to sleeping either on top of Beth, or wedged in on the end of her pillow, rather than on the end of the bed where Sophie had slept before – so we get pretty vocal complaining about that too. Remind me again, why is it that we have a pet?

Visual Source UnSafe

I have to say, I know a lot of developers who aren’t exceedingly impressed with Microsoft Visual Sourcesafe. Most people acknowledge that it is a pretty basic source control system, and really only any good for simple projects. Having said that, I’ve used it for over ten years, since before it was a Microsoft product. (The package was originally produced by One Tree Software, founded in 1992, and then taken over by Microsoft in 1994. You can read a blog entry by one of the original three people who set up One Tree, and went to Microsoft here.) Aside from a big disaster with a database with an early version, I’ve not usually had too much problem with the product. Certainly with the more recent versions, although I knew people who had encountered problems, for the sort of basic source control stuff I was doing, it had been reliable, until today.

The problem I had today came about as a result of us having to move our SourceSafe database. This should be a relatively straightforward process, as a SourceSafe database is basically just a collection of files. Anyway, the problem was that the database didn’t copy cleanly, failing on 37 files, that for some reason it couldn’t copy.

On that basis, I thought I’d use the SourceSafe database analysis tool to see if there were any problems – which produced several pages of files that were apparently corrupt, and suggested that I run the analysis in fix mode, to fix the problems.

So following the instructions, I ran the fix, and this claimed to fix the problems, so I tried the copy again, and it managed to copy everything.

At this point we opened up the database in SourceSafe, and started spotting problems. Amongst a catalogue of problems we had files and projects totally missing, whilst others had the wrong files in them. All in all it was a total nightmare, the tool you rely on to keep your work secure had basically scrambled it. The most recent backup was from Tuesday, so currently we have the backup, alongside the semi-corrupt database.

Anyway, at this point I had a look around the web, and came across an interesting article on SourceSafe defects, and some pages on SourceSafe internals which made interesting reading when reviewing some of the things that had been done to our SourceSafe database over the past year or so. Having read some of those, I’m amazed we didn’t have problems sooner.

So, I have to say that my opinion of SourceSafe has definitely got worse, and the key mantra when using it is to not try to be clever. Particular techiniques to avoid are deciding to restructure you source tree part way through a project, and trying to generate new project release trees using branching and sharing.

Having said that, it is worth bearing in mind that the current version of SourceSafe that is used with Visual Studio 2003, is a patched version of the version that shipped with Visual Studio 6, a good few years ago – however this year it is finally being updated, with a new release, plus a new big brother, Team System. Hopefully as a result of today things will be put in motion to upgrade to something where the repair tool doesn’t make the problems worse!!!!

The Dilbert Blog

Browsing around the web last week I came across a new blog called The Dilbert Blog. Now I, together with 36,153 other Bloglines users have been enjoying the daily Dilbert comic strips, however this is something slightly different. Although it is called The Dilbert Blog, it is actually Scott Adams himself, the man behind the cartoons, blogging about anything and everything.

So far we’ve had an explanation about why the online version of a recent cartoon included a lawyer with a porpoise, but the printed version didn’t, a discussion about crime, and today a brilliant description of why Scott likes technology. If you’ve ever read any of Scott’s books you’ll know what to expect. Definitely a great addition to my blogroll.

The Dilbert Principle Dilbert: The Joy of Work The Dilbert Future: Thriving on Stupidity in the 21st Century