...as I have two out-of-town excursions to deal with this month.
Next week, two days in Seattle. I'm somewhat interested in the product I'll be seeing, and the people from the company are just about the best in the business when it comes to dispensing information and being personable after work hours.
There's a computer connection -- justifying Seattle as a location -- and that's the part where my eyes are beginning to glaze over a week in advance. I could go into a long screed about this, but will confine myself to saying that the uses of computer technology being envisaged fill me with...ennui.
Otherwise, I could easy avoid most of the Pacific Northwest and be perfectly happy, thank you. I did my time in Seattle many years ago. This visit will not rekindle pleasant memories.
Two days will be enough.
Two weeks later, I'm off to Montana. Two days will not be enough there, and I am dropping none-too-subtle hints that I might like to hang around a few days to sightsee. No, I'm not trying to get my hosts to come up with extended accommodation or anything of the sort -- though I wouldn't be the first in my field to ask for such a perk, believe me -- but they can render some logistical assistance, for which I would be grateful.
Montana is one of the few states -- Wyoming is another, as is North Dakota -- I have never visited. Well, there is a fourth, but it's not on my must-visit list. Everything I've seen suggests I need to look around, and I can't do that during the program. Not as much as I want, anyway.
At least the flights for these trips are relatively short. And neither requires me to set foot in any United Airlines aircraft. Seattle is a direct flight, and Montana is a one-stop via Denver, I think. I can do that. For short events, a small carry-on bag and a briefcase are all I need.
I needed to get out of here for a while anyway. Neither of these is my ideal choice when it comes to what I'll be doing and where I'll be doing it, but I'll take what I can get.
They might even be fun trips....
1 hour ago