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
You Get What You Pay For | 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

You Get What You Pay For

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
Oct 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
Oct
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

I’m going to link up to Jo-Lynne’s What I Learned This Week carnival a couple of days late.  I apologize to anyone reading this who now thinks it is Tuesday.  No worries: the week is almost over and trick-or-treaters will soon be descending upon your door.

Last week, after 8 years of service, our toaster that we got as a wedding gift bid us farewell.  It was only toasting one half of whatever was being toasted.  I think I lasted maybe 2 days of flipping the toast over and toasting it again before I was done with that.

I told my husband I didn’t want to shell out a lot of money for a toaster.  And believe me, if you haven’t been toaster shopping lately, I’m here to tell you there are some ridiculously expensive toasters out there.  I think they not only provide you with toast but pay your bills  and raise your children as well.

I settled for a 4 slice toaster that was 15 bucks.  I was so proud of myself for being frugal and ignoring the higher priced toasters that seemed to be calling out for me.

Here’s where the “you get what you pay for” part comes in.  This is a “no frills” toaster and apparently being able to fit your entire piece of bread in the toaster…is considered a frill.  I love when I put in a frozen waffle and the top of it is sticking out.  It’s a great way to get your day started!

Lesson of the day: Sometimes it’s best not to skimp on certain things. And a toaster is one of those things!

19 Responses

  1. Kim Says:

    Ha Ha Ha
    Feel free to come over and use mine when needed.
    I also have an extra toaster oven and toaster in my cabinet that I am willing to donate to the cause.
    Remind me not to ask for toast at our house!
    Ha Ha Ha - still laughing about this!

    PS: I’m expecting a good comment from your Dad - I miss those!

  2. Kellyn Says:

    Oh man! We got an inexpensive toaster and it is actually the best one we ever had. By inexpensive I do mean about $8 at Target three years ago.

  3. Your Father Says: Says:

    Do they still give toasters as wedding gifts?? Thought that ended in the 70’s when your Mom and I were married. Buying a toaster is like buying a roast. It’s either good or it’s bad…there is no in between. The toaster works or it doesn’t..the roast is absolutely tender or full of grissly fat. Your mom and I had a 2 slice toaster when there were 5 of us…When you all left, we bought a 4 slice toaster????. We’ve only used one side and complain that it’s not doing a good toasting job. Have we ever thought about using the other two?? No..You can’t change..it’s only the two of us…we just keep using the same two and complain that it doesn’t toast well. Maybe we could switch toasters..we don’t do waffles, so yours might work for us and you could use the two sides of the 4 slice toaster that we have never used. Like the roast, this idea of switching toasters is a 50 - 50 chance. Maybe one of us could be a winner. Love ya. Dad

  4. Musings of a Housewife Says:

    Hysterical. You have such an entertaining writing style. It sounds just like you’re talking to us.

    And then your dad just picks up where you left off. Love it!

  5. lora Says:

    I have a post in my head about what happens to all your stuff when you’ve been married for ten years.

    It’s all ten years old and falling apart, that’s what!

    I’m sad to hear that you know all about this horrid, horrid phenomenon!

  6. Iva @ This Side of Perfect Says:

    As I’ve gotten older (did I really just type that?), I’ve learned that you really do get what you pay for! We now shop for clothes at JC Penny’s instead of Walmart because the clothes last longer. When teamed up with a coupon, I end up spending just a few dollars more for the higher-end clothes.

  7. baidu censor Says:

    Other countries censor content and not just rogue regimes such as the Iranian mullocracy. Poor people! http://www.baidu.com

  8. playstation codes Says:

    The advantage with these PSN cards is that they are easy to
    are and implement easily accepted by most of the
    gamers of Play - Station. Promotion of online game is also completed
    depending on its performance which helps the players to buy
    these online games following that bank account. It will be a
    huge undertaking but it will be a lesson learned the hard way not only
    for Sony but for other companies who have the same kind of lapse security in place.

  9. לחץ כדי לקרוא Says:

    Quality content is the secret to be a focus for
    the people to visit the web site, that’s what this web site is providing.

    Feel free to surf to my webpage - לחץ כדי לקרוא

  10. gucci vintage purse Says:

    Hey there! This post could not be written any better! Reading this post reminds me of my good old room mate! He always kept talking about this. I will forward this write-up to him. Fairly certain he will have a good read. Thanks for sharing!
    gucci vintage purse http://filippos.org.uk/wp-includes/gucci/9akgucci-vintage-purse-@=-46al.php

  11. Terri Says:

    I’ve been exploring for a bit for any high-quality articles or blog posts in this sort of area .
    Exploring in Yahoo I at last stumbled upon this web site.
    Reading this info So i’m happy to show that I’ve an incredibly excellent uncanny feeling I found out just what I needed.
    I so much indubitably will make certain to don?t omit
    this web site and give it a look regularly.

  12. Fern Says:

    WOW just what I was searching for. Came here by
    searching for Crazy tales from a normal life

  13. שירותי שיווק באינטרנט Says:

    Hi my family member! I wish to say that this post is awesome, great written and come with approximately all important infos.
    I would like to look more posts like this .

    Feel free to surf to my web blog; שירותי שיווק באינטרנט

  14. מחירון דלתות פנים Says:

    Great information. Lucky me I recently found your blog by chance (stumbleupon).
    I have bookmarked it for later!

    Here is my webpage: מחירון דלתות פנים

  15. Nestor Says:

    Hi there would you mind letting me know which web host you’re working with?
    I’ve loaded your blog in 3 completely different browsdrs and I must
    say this blog loads a lot faster then most.
    Can you suggest a good web hosting provider at a honest price?

    Many thanks, I appreciate it!

  16. Bret Says:

    naturally like your web-site but you have to take a look at the
    spelling on several of your posts. Many of them are rife with spelling problems and I to find it very bothersome to tell the truth however I will surely come again again.

    web site; Bret,

  17. http://www.buzzfeed.com/ps3emu/how-to-play-the-ps3-emulator-on-your-pc-141rl Says:

    I quite like reading an article that will make men and women think.
    Also, many thanks for allowing me to comment!

  18. buy nba 2k16 mt Says:

    thank so considerablya lot for your internet site it assists a lot

  19. http://www.tapuz.co.il/blog/net/userBlog.aspx?FolderName=ormisrael Says:

    I was curious if you ever thought of changing the
    structure of your website? Its very well written; I love what youve got to
    say. But maybe you could a little more in the way of content so people could connect with it better.
    Youve got an awful lot of text for only having 1 or
    2 images. Maybe you could space it out better?

    my blog post http://www.tapuz.co.il/blog/net/userBlog.aspx?FolderName=ormisrael

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.