Thursday, November 09, 2006

Spoiled

When Kevin and I first started dating, he'd just started a new assignment where he'd be gone for ten days and then back for four. That was our relationship for a while, and then he started working for five days, home for a standard weekend. Not an ideal situation, but we managed to work with it since I was working mostly nights at the store anyway.

Recently, though, he was working in Detroit and could drive home every night. It was nice because we would get to see each other randomly during the week, instead of waiting for Friday night to come around. Then tonight, I found out that instead of going back to Kentucky for five days like he was doing before he headed to Detroit for some political work, Kevin will be headed to Little Rock, Arkansas to work ten-day stretches on a Volde-Mart campaign. And THEN he'll most likely be flying to DC to spend the holiday with his mom and sister.

Of course, if he goes straight back to Arkansas, that will be... *does the math* ...many days without seeing my boyfriend. And since I don't have a cell phone, it'll be limited contact as well. Back to emails and missed IMs, I guess. This sucks, dude.

I don't mean to sound like I am complaining, but it's not easy for me to say what I mean without it coming across the wrong way. It's hard to be in a relationship where you can hardly see one another. I'm just glad that we've been able to go this long in a similar situation. I'll just take it one day at a time and try to find things to make our time together more meaningful.

On that note, anyone have any suggestions for me? (Kevin, no peeking!) Heh.

And here's a bit of the funny from the boy:
Kevin: I was gonna say I'd bring you something nice from arkansas, but I don't know what nice things they have that are from arkansas
Kevin: I only know that hogs, Wal-Mart and Bill Clinton are from there
Kevin: there is already a few wal-marts here, a hog is hard to take on a plane...
Kevin: maybe I'll have to bring you an ex-president
Heto: who doesn't love bill?
Kevin: that's what got him in so much trouble

No comments: