whenever it comes up in conversation that i do virtually no “wifey” cooking for my husband people tend to be surprised or jealous. and yes, i am using “wifey” in the most sexist terms. i mean it to say, i don’t decide what we will be having for dinner, go to the store, make a meal, and have it hot and ready when dinnertime rolls around.
when i say this, i feel like it’s always seems as if i’m getting out of an unpleasant chore. but here’s the thing: michael would hate it if he were to come home to meals prepared without his consent. he always, always wants a say in what he’ll be eating for dinner. if he doesn’t feel like eating chicken and vegetables, there’s no way he’s going to eat it. this may sound really bratty – and really, it probably is – but the result is that michael does most of our cooking because i am far, far less particular and will usually eat whatever is set in front of me. (so i win!)
but, from time to time, if there is something i really want, i’ll go ahead and prepare dinner and hope it will pass.
so, last week i saw a recipe for homemade ricotta gnocchi and it just sounded SO good. i thought about it for days before finally deciding that is what we’d be having for dinner without the usual democratic-dinner-decision-process of our household.
here’s how it went:
mix it all together, roll it out, slice it up. done.
boil for just a minute or two.
i served my made-from-scratch-gnocchi with made-from-scratch sauce i’d made earlier in the week and added some cream because we LOVE cream sauce.
so what was the verdict…?
well, the recipe emphasized that the lighter and fluffier the better and to not over mix, but apparently (according to michael) it was TOO light and fluffy and the texture was like soggy bread. (note: i thought it was delicious and almost ate the whole batch)
(more for me!)
so, THIS, my friends, is why i don’t cook for my husband! 😉