What 6000 Miles Can Mean

For the past 10 days, Matt has been in Amman, Jordan. The trip is mostly business and partly pleasure, and it marks the longest amount of time that we’ve spent apart since I got pregnant. I spent a few days in Denver around the 16th week of my pregnancy, but there’s something inherently different about Denver and Amman. I think it’s probably the 6,903 miles that separate the two cities, but I could be wrong about that.

Matt was a mess before he left. I couldn’t figure out how to help him, how to calm him down, how to make him see that this trip would be an incredible experience, an opportunity that he simply couldn’t pass up, and one that truly couldn’t have come at a better time in my pregnancy (namely, before the baby was born). The night before he left he tossed and turned, anxiety crippling his features in a way that I have never seen in the 11 years we’ve been together. It was almost too much to bear, and I complained to Julie that I wish he’d just LEAVE already, because it was too hard to not understand what he was going through and not have any power to help him.

But I was talking to an old and dear friend about it over the weekend, and she was so insightful. “Being there for you is pretty much the only thing that Matt can DO at this point,” she said. “When he’s not there, then it’s almost like he’s not part of it, because he’s not growing that little person, not feeling the aches and pains, not going through the changes that you’re actually going through.” And all of a sudden Matt’s anxiety made sense. The one thing that he can do to usher us safely through this pregnancy is to help usher me safely through this pregnancy. It’s awfully hard to usher when you’re 6,000 miles away.

But the strangest thing about Matt being gone is that it’s forced me to spend some time alone with my own thoughts about pregnancy and motherhood. A few weeks ago, this would have been a very bad thing. I would have thought about all of the ways that I was already a terrible mother, because I was likely doing something terribly wrong to hurt our little bean. But now, a few good appointments under my belt, regular movement in my tummy, and the occasional visible-from-the-outside kick near my belly button, the thoughts aren’t all anxiety-laden. Even as I sit here licking the remnants of a Milky Way from my fingertips, I know that I’m not (yet) a bad mother.

But what I realized the other night was just as shocking to me as if the bean had screamed “I hate you!” from inside my uterus. I realized that I was okay. Rather, I realized that even with Matt not there, I was doing alright, and that the bean and I are a new lumpy little unit.

I can’t explain why this realization was so jarring to me, except to say that I will look back on it as the first time that I realized that I am actually going to be somebody’s mother. The mother to somebody who will need me for most moments of their first few months, somebody who will expect me to calm their fears, exalt their accomplishments, and be present for the little and big moments of their life. Someone who will have every right to expect my unconditional love, and who will someday shout at me for smothering them. It was both a terrible and an amazing realization, because it made me feel wonderful to feel so needed at the exact same time that it made me feel terrible for needing Matt a little less.

I haven’t shared any of this with Matt yet, so when he reads this post he’ll probably feel sad. It flies in the face of what it is that he probably feels like he can do to make this pregnancy easier for me. If I don’t feel like I need him when he’s gone, then what can he give me while he’s here?

The truth of the matter is that by leaving for Jordan, he gave me something he couldn’t have given me if he stayed. He gave me confidence. He reminded me that I’m strong enough to weather a long-distance relationship, that missing someone (for a little while) can be a good thing, that I can be the type of partner who recognizes a great opportunity for her husband when she sees one. But more than that, by leaving, he made me realize that I will be the kind of mother I want to be, the kind that fails (by her own standards) many many times, but succeeds many times too. I already know exactly what kind of father Matt is going to be, because he will be the man that I married, the man who loves me and our someday-bean unconditionally and feels anxious at the thought of not being able to be there for us. I am starting to realize that together, we’re going to make a pretty good team.

Matt will be home in 2 more days, just in time to celebrate my 32nd birthday. I can't wait for him to come home, can't wait to hug him and kiss him and see his face as he marvels at how much my belly has grown in the 12 days he was gone. I have no intention of being apart from him for the rest of this pregnancy; I AM better off when he's around. But in the interest of donning a pair of rose-colored glasses, of looking on the bright side (finally), I think that this trip was a good thing for all of us, for me, and even for our growing little bean.

Now That's High-Class

Yep, that's right. The Charlotte airport men's room has an attendant. For real! He'll hand you a fresh paper towel (from the automatic paper towel dispenser) and wish you a good day. On your way out, you can grab a tiny cup of mouthwash and drop a single in his tip jar. You heard it here first: Charlotte airport is like the freakin' Rodeo Drive of airports.

Down South

I'm heading down to Raleigh, NC, for another fun-filled week of troubleshooting routers and whipping recalcitrant traffic emulators into shape. Should be good times. At least there's tons of great barbecue in the area.

By the way, sitting in the Charlotte, NC, airport right now. When I stepped off the flight from Boston, I was slapped in the face by the hot, stickiness of 90+ degree weather. I guess the South finally recognizes that it is, in fact, summer.

Sometimes I Wish I'd Just Dialed In

I've been traveling for business every week since mid-April. Last week I was in Colorado Springs for a one-day meeting. Let me just say that traveling to Colorado for a one-day meeting is NOT worth it. First, it takes a whole day of travel from Boston on either end, since there is no such thing as a red-eye out of Denver or Colorado Springs. Second, there is no such thing as a direct flight from Boston to Colorado Springs and back. Third, and finally, a spate of "tornadic activity", while cool from the ground, makes attempting to fly through or around it a complete pain in the ass.

So the facts are these: My flight from Boston to Denver was delayed a mere 20 minutes, but once airborne those 20 minutes stretched to two-and-a-half hours as we were re-routed up over Canada (twice!) to avoid heavy thunderstorms over the Midwest. I was sitting in the middle seat in the back of the coach cabin, which means there's only 2 inches between your nose and the back of the seat in front of you (less when the asshole in front of you leans his seat all the back), with a tremendously obese woman to my right and a young woman with her 18-month-old son to my left.

Upon finally reaching Denver, I'd missed my connecting flight to Colorado Springs. And then had to deal with United's inept customer service reps as they tried to rebook me. Unfortunately, most of this alleged rebooking involved me running back and forth from gate to gate, being told by the gate agents that the flight was closed or delayed and that I would need to talk to customer service. Their excuse was along the lines of "the weather forced us to cancel a bunch of flights and, of course, the best option for us was to fly all of these passengers to Colorado Springs and make it someone else's problem."

So here I am with a standby ticket for the last flight (already oversold) to Colorado Springs and I have to be at the meeting at 8:30 the next morning. And I do the only rational thing left: I call United, cancel my leg to Colorado Springs, rent a car and drive. In the end, I arrived at my hotel 5 minutes after my rebooked standby flight was supposed to have taken off from Denver.

The moral of the story is twofold: 1) Never fly United, and 2) Denver is close enough to anything in Colorado to make connecting flights not worth the hassle.