Deprecated: Assigning the return value of new by reference is deprecated in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/http.php on line 61

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method adsensem::init() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/plugin.php on line 339

Strict Standards: Non-static method adsensem::setup_is_valid() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 117

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method adsensem::init_widgets() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/plugin.php on line 339

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 152

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method Add_to_Any_Subscribe_Widget::init() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/plugin.php on line 339

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/mylinks.php on line 287

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/mylinks.php on line 288
Summer Craziness | muzbeecrazy

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 55

Summer Craziness

Posted by Shannon on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 55
Jul 29th, 2009

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 55
2009

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 55
Jul
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/functions.php on line 55
29

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/mylinks.php on line 287

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/mylinks.php on line 288

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method adsensem::filter_ads() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-includes/plugin.php on line 166

Strict Standards: Non-static method adsensem::filter_ad_callback() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 245

Strict Standards: Non-static method adsensem::filter_ad_callback() should not be called statically in /homepages/19/d229128027/htdocs/muzbeecrazy/wp-content/plugins/adsense-manager/adsense-manager.php on line 248

Wow! I feel like I blinked and the first part of summer is over.  Let me assure you that the second part of summer will probably drag on for an eternity. Why such the pessimistic outlook, you ask?  Where should I begin?

My husband(who I will be referring to as simply A) plays deck hockey at a local sports complex.  Once a week, he meets his friends for their scheduled games and once a week I watch him crawl in the door after his games.  He is always coming home bruised and battered.  I thought he learned his lesson a few months back when he took a hockey ball to the eye, but I was just being silly I guess.  Last week I watched as he limped on in the house while his friend carried his equipment.

“I blew out my knee,” A says.

“And it begins,” I thought to myself.

After a painful night’s sleep, we got him into our doctor’s the next morning.  She recommended an MRI.  That was quickly scheduled for later that day.  As we waited at the pharmacy for his crutches, it became clear to me that I was going to have to call out of work to get him to his MRI.  I really dislike calling out.  I become overwhelmed with guilt.  So as we were driving home from the pharmacy, I asked him if he could just drive himself to the MRI.  The poor guy tried from the passenger seat to mimic the motions of driving and exclaimed, “It really hurts!”

WHAT!?  I never said I was going for wife of the year! Needless to say, I did not go to work that evening!

The next day, we got the results of his MRI.  It rambled on about sprained ligaments, bone bruising, torn meniscus, and torn ligaments.  A same day appointment with an orthopedic was made.  He moved A’s leg around all over the place while saying, “Does this hurt? Does this hurt?”  I think it was pretty clear from the facial expressions that it hurt…PLENTY! The doctor then proceeds to take fluid out of his knee.  Then says, “We need to go in there and fix your knee surgically.”

Through this whole ordeal, I thought A was going to pass out numerous times.  But we’re not even done yet.  ‘Cause now we gotta talk about the surgery.  My sweet husband does not do well with this kind of talk.  There are 2 ways to fix a torn ligament.  They can use his own hamstrings which is a more painful and longer recovery, or they can use one from a cadaver.  A’s  hand was over his face as he laid there on the table.

“You don’t have to tell me today. But let me know soon because if you want the cadaver part I’ll have to order it,” says the doc ever-so-nonchalantly.  Meanwhile, I’m looking around for the smelling salts because I thought this would surely send A over the edge.  But somehow, he managed to stay conscious.

Surgery is scheduled for the end of August.  Followed by at least 2 weeks of recovery and then physical therapy.  It is going to be a LONG 2+ months.

AND if you ask A if he is done playing deck hockey, his answer is: “No.”  See, there I was being silly again thinking he would now realize that his hockey days are over! He really knows how to take one for the team, doesn’t he?

9 Responses

  1. Iva @ HorizontalYoYo Says:

    How old is A? Late 20s? Early 30s? A little banged up knee won’t keep the man from playing hockey…but hopefully after 2+ months of therapy, he’ll adapt are more age-friendly sport. Hiking, maybe?

  2. Kellyn Says:

    My first thought was “You mean you don’t already have crutches?” lol

    My husband is the same way, no fighting him on it either. He wants to play volleyball, so he does. Pain and all.

    I hope he has a…speedy two month recovery. And that your hair stays in your head, and not pulled out.

  3. Sarah Says:

    As the saying goes, boys will always be boys still applies to men lol.

  4. lv alma pm Says:

    louis vuitton usa ipad louis vuitton lv website lv purse parts palermopm m32630 louboutin un bout palermopm lv handbags on sale figheri gm 40354 louis vuitton lv card wallet figheri pm portobello pm louis vuitton 2011 christian louboutin illusion pump christian louboutin replica christian louboutin red bottom heels louboutin rolando cheap red bottoms heels

  5. Teona Says:

    Karen, lovely nslewetter once again. Thanks! Fab article! Oh yes, I agree with C.Louboutin but wonder whether it was the colour RED or the place of the colour that bothered him and makes sense not to be copied. Have YSL had put purple on each sole of the shoe I think it would cause the same distress Or at least I would have thought Louboutin came out with a new spring/summer line of course it both proves your point the importance and impact of coloursI remember being very upset when I saw Jamie Oliver’s series and ads one year after I started duda does under the name Jamie does..Italy, Jamie does Spain Of course I am sure Jamie has no idea bout duda does nor his producers (otherwise they would hire me he he) but I felt like they stole it from me Have a fab May everyone!Duda x

  6. Bootz Says:

    The unique thing about this idea is that the cooulr is there but doesn’t overpower the shoe so someone (a girl or a guy) who wants to be a little bit risque can be so without going all out and wearing full red shoes. Kind of like having a bright cooulr or a pattern on the inside of your coat or your bag you know it’s there (teehee!) and it makes you feel like you have broken the mould just a little bit but you can still blend in .

  7. Jailyn Says:

    cheap health insurance canada insurers cheap viagra home insurance.com

  8. Coltin Says:

    discount car insurance

  9. Smithe7 Says:

    I am now not certain the place you’re getting your info, however good topic. I needs to spend some time learning more or figuring out more. Thank you for magnificent info I was on the lookout for this information for my mission. edcafefgcfadaage

Leave a Comment




XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.