Monthly Archives: December 2005

A sign that ticket prices are too high

Les Misérables is in town, and I would love to see it. I’ve seen it three times, but it’s one of those shows that I could see a million times and love it more each and every time.

Problem is: the tickets are minimum $200.00. The best seats still available are over $300.00. $300.00 for 3 hours of entertainment? Is it that really worth it?

In London, front row seats are about £40 ($70). A quick search turns up a flight for $419 from Dulles. So… for $300 I could see Les Misérables here, or for $490.00 I could fly all the way to London and see it.

Gift of the Magi

While I was shopping for a gift for my dad I must have mentioned to somebody something about how someday I wanted to build model ships. My dad caught wind of it, and on Christmas Eve I opened a nice set of knives and razors suitable for working with small wood parts. I was really confused. My mom got it, and laughed. I was still confused.

Later that night, my dad opened his model ship, and I handed him the knives which he had bought for me. Very funny. 🙂

On Fixing Computers

As the family’s computer guy, I often get asked to fix, maintain, look at, improve, or otherwise modify my family’s computers over vacations. This Christmas vacation is no exception. While I was at my brother’s house he asked me to look at his computer–remove spyware, make sure everything was running smoothly. I updated Spybot to 1.4, ran Ad Aware, and removed a bogus web search toolbar. And that’s about it. All-in-all, the computer was running smoothly as-is.

A few hours later, I got called to look at it because a new error message was being displayed–by Norton Internet Security. The anti-virus e-mail checker was disabled. I think this is what happened: It turns out that running Spybot had turned on the Windows Firewall, even though Norton had its own.

On the one hand, I probably could have read the descriptions of the problems Spybot had found and realized what it would do. On the other hand, why did Spybot find a problem when there really wasn’t one?

Computer software, including operating systems and the applications we run on them, has gotten far too complex for us to understand the implications of even simple operations.

Everytime we install an application on Windows, it makes changes to the file system, the registry, the start menu, and more. If it’s a system utility, it can modify much more.

And don’t tell me it’s any better on Linux. You have to deal with the potential of mismatched shared libraries every time an application is upgraded.

There a couple of technologies that I see as easing some of these problems:

  • .Net – xcopy deployment (for the most part), easy to use XML config files. Drop in and play for simple apps. Many Linux apps work well like this, why not Windows?
  • System change monitoring – like MS Anti-spyware, it notifies you whenever a system change occurs and lets you stop it before damage is done. What if we had a system that allows you to set what kind of changes you want to be notified about? What if it monitored a much broader set of features than today? This method presupposes a fairly good knowledge of computers. I like MS anti-spyware, but I wonder what people thing when it brings up a window asking whether to continue with a registry change, or run a script. Most people simply dismiss things like that, which is unfortunate.