It’s three months away, and I’m counting the days.
My prep work for my very first PASS Summit continues. I’m still waiting to hear as to whether or not my PowerPoint slides are accepted and good to go, or if I need to make any tweaks to them. I’m waiting to announce my presentation schedule (per PASS rules, I’m not allowed to announce it until they do). (Edit: the schedule has been released! I’m speaking on Friday, November 8 at 8 am PST!) There has been plenty of chatter on Twitter (which I’ll get to in a little bit) in regards to the approaching event.
I did have one setback, which didn’t make me happy. I had originally scheduled my flight home for the morning on Saturday, November 9 (which reminds me — travel tip — I discovered that it was actually cheaper for me to buy two one-way tickets, not one round-trip ticket). Per the advice of nearly everyone who’s been to PASS Summit before me (especially Matt Cushing), I was told that I should stay through Friday night and book my flight home for Saturday. I took that advice to heart, and booked a flight back to the East Coast for Saturday morning.
Unfortunately for me, American had other ideas. My flight, which was originally supposed to be 8 am on Saturday, was switched to 10 pm on Friday. To put it mildly, that did NOT make me happy. I fired back to American with a very angry email — my wife practically had to force me to NOT use any — let’s just say — colorful language in my message. I looked into changing my flight. The available options fell into one of two categories: either the schedule didn’t work for me, or the airfare was absolutely ridiculous. There was no in-between. (And if that wasn’t enough, I have something going on that Monday, which precludes me needing to be home at a reasonable time.) So, for the moment, it appears the best option is for me to keep the flight to which I’ve been switched.
It is exactly for reasons like this why I’ve come to hate flying. It is also one of the biggest reasons why I prefer taking Amtrak. I seriously considered it for this trip, but rejected it because of schedule constraints. I do love traveling by train, and believe me, I would’ve enjoyed taking 3-4 days to take a train across the country, but that’s a luxury that I just don’t have for this trip. (I’ve toyed with the idea of taking the train cross-country as a vacation idea — i.e. I wouldn’t be taking the train to get to a vacation. I’d be taking the train as the vacation! Maybe someday…)
And in addition, American Airlines has been dropped to my list of “airlines of last resort” (if I ever bother flying with them again at all).
Anyway, as I mentioned above, Twitter has been very active in regard to PASS Summit. I reluctantly joined Twitter last month. I didn’t want to join, but it’s the medium of choice for just about everyone involved with PASS, and my acceptance as a PASS Summit speaker pretty much forced my hand.
I posted my frustration at American Airlines on Twitter, and as a first-time PASS Summit attendee, asked #SQLFamily for their advice. A number of people told me that it wouldn’t be a big deal. Sea-Tac Airport would likely be busy on Friday night (which was one of the big reasons why I booked Saturday in the first place), but multiple people, including Matt Cushing and Grant Fritchey, told me that PASS generally doesn’t schedule events for Friday night. Mostly, what I’d miss is the opportunity to get together with #SQLFamily friends. And therein lies the rub.
The flight switch also affects other plans. I sent a message to my AirBnB host saying that my stay might end up being one night shorter than I planned. I want to wait a while before making that determination — for all I know, American might switch it back to Saturday. Dear airline industry: it’s not like we travelers have plans or anything like that. I swear that some of the things they pull are downright criminal. I’ll say it again: there’s a reason why I prefer Amtrak.
In any case, my plans continue to roll along. It should be fun! November will arrive before I know it.