two places at once.

This whole week I’ve been excited about this weekend. See, it’s springtime here in DC again, the cherry blossoms are out, it’s in the seventies (hard to believe we had snow last weekend); DC can really be nice in spring. So, my thoughts have turned towards my George Foreman grill and having some friends over for a multipurpose cookout on Saturday.

A multipurpose cookout? Why not just call it a BBQ and get it over with?

Well:

1. I have a great respect for real BBQ, and since I’m not smoking my own meat, it’s not really a BBQ,
2. A proposal my wife was on recently was accepted by the VLA, and no one has thrown her or her team a celebration yet,
3. I have a lot of stuff to give away before the move and thought having people over would be a good way to do so, and
4. When veggie burgers and grilled vegetables get put on the menu, it becomes less of a meatfest and more of a cookout.
5. It’s my party, I’ll call it what I want.

So, where was I? Oh yes. I’ve been looking forward to this for the past few days, invited a few friends over, the usual stuff. Aside from the possibility of rain (which is now receeding), things looked smoky good.

At the same time, I’ve been looking forward to going down to Williamsburg this weekend to pick up my wedding album.

On Saturday.

So I’m on the phone with Merrystar last night and explaining all about the menu and how I think we’ll still have it, and then I break in to how excited I am about going to get the album, and maybe we could stop at the outlet stores on the way down at Potomac Mills.

Suddenly it hits me: I’m planning two events, in two cities, for the same exact time.

“Did you know you went to bed at 4 am last night?” my wife asks me. I realize it’s a relevant question.

“Uh, no, I didn’t,” I reply, though that explains a heck of a lot, like why I thought I could be in two places at once.

Note to self #47082: check to see if social schedule requires advanced technology before issuing invitations.