The part of my wedding I was most excited for was the honeymoon, which makes perfect since because I was scared out of my mind about getting married in the first place. Nothing overpowered that sense of fear I felt for the many months leading up to the big day, but the thought of heading out on a honeymoon where I could have a break from those stresses while on my very first vacation as a grownup got me pretty excited. And not much else about the getting married process was exciting. Planning the wedding? Nope. Watching Casey pick out things for our registry? Nope. Finding clothes for the wedding? Nope. Pictures? Nope. So, the honeymoon landed its spot near the top of my pre-marriage excitement list almost by default.
For our honeymoon, Casey and I decided to head to Vail, Colorado. For those who are unfamiliar with Vail, it’s a lot like Aspen, Colorado. Meaning, it’s primarily a ski town for the rich, the famous, and the even more rich. We found out pretty quickly that Vail was not a town for a pretty poor newly wed couple and the memories we collected on that honeymoon have been almost completely negative. The honeymoon consisted of us locked in several arguments all while we couldn’t afford to do anything in Vail.
After returning from our adventure to Vail, we both decided it was a mistake, and if we had it to do all over again we would go on our honeymoon a year after our wedding. Of course, these reasons are our reasons and they aren’t going to fit for everyone. We were two people who only knew each other for about 6 months before hand and we did not live together before our marriage. We were also very young, Casey having turned 19 years old weeks before the big day and me having turned 22 a few months before the big day. Some of the reasons we don’t think newly weds should go on a honeymoon aren’t going to fit couples who are more familiar with each other and who are already financially sound. With that in mind, here are 10 reasons not to go on a honeymoon:
More on Babble Dad: