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
What’s it Going to Take? | 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

What’s it Going to Take?

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
May 15th, 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
May
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
15

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

I’d like to share with you a picture of our light fixture in our master bathroom.

lights

Alright, let’s start with the obvious.  It ain’t got no alibi, it’s UGLY! When we had the house built, we decided not to upgrade any of the light fixtures because we figured we would do that on our own.  Here we are 5 and a half years later, and it is still up.

Excuse me?  What’s that?  That wasn’t the obvious statement you had in mind? Oh.  Right.  So, when do you think we will change the light bulbs?  I have a pretty good guess.  I can picture how the whole scenario is going to play out.  It will probably happen in the middle of the night, when the kids are sick or in need of the bathroom. We will go to flip on the switch and …POW! Darkness.  And then I’m sure a string of poor language will be muttered as we wonder how this happened.  It will be memorable.

Can you imagine when we actually replace the light bulbs? There will be such bright light in our bathroom, I’ll need my sunglasses and some sunscreen.

Until then, I’m sure we will just wait out the life of our one last lonely light bulb.  Shine on, little buddy!

8 Responses

  1. Kim Says:

    I’ll bring over my bulbs since I don’t have that fixture anymore. We can change the bulbs and then have a glass of wine celebrating our accomplishment!

  2. One Mom Says:

    HA! We have the same light fixture and I think it’s been here for going on 30 years…I think since the house was built and we’re the 3rd owners..only all of our bulbs are working…it must be like putting your makeup on by candlelight!?

  3. terra Says:

    Cracked me up, I am sitting below a burnt out bulb right now, I am getting up to change it - it has been this way for a month…I am not lazy. Just well, lazy.

  4. terra Says:

    oh crap, the bulbs we had are not the same as the others and so now one is REALLY bright and the other two are not AND I had to dust looked inside to change bulb and GROSS…Thanks alot Shannon.

  5. Mel Says:

    I could have sworn that you came and took a picture in my bathroom. I’m gonna go change those lightbulbs now since you reminded me of how it can go horribly wrong if I don’t get it changed. Enjoy your weekend.

  6. Kellyn Says:

    I hate those light fixtures, but how expensive the bulbs are is what kills me. We would do the same thing in our old place, let it go until we moved! Then we had to replace them. lol

  7. Musings of a Housewife Says:

    Okay, now THAT is pathetic. ;-)

  8. Your Father Says:

    In the time it took to go find the camera to take that picture, then upload in to the story that you stopped doing everything to write, you could have replaced all 3 of the bulbs. But I am going to go out on a limb here and bet you do not have any replacement bulbs in your house or know what the wattage of the bulbs are !!!!!! Unscrew a bulb, look around it and see if it says 40W or 25W, then take your gift card you won for your bottled water money saving tip, and go to that store and buy that bulb wattage, take them home and replace them. I will be down on Memorial Day. It will be done before that …. Right!!????!!

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.