The other day I decided by George, I was going to cook dinner. Like, actually cook dinner. Not just reheat something.
You cooks out there may be scoffing, but this was major for me. One of my goals since becoming a full-time domestic engineer has been to, well, become domestic. I’ve always fixed dinner for the two of us, but more often than not that entails simple actions like boiling hot dogs, toasting cheese on bread, pulling a pizza from its plastic wrapper and popping it in the oven. Simple stuff.
So the other day I selected a recipe from a cookbook and planned to make it. I was going to make corn bacon chowder. I went to the grocery store and bought supplies we normally don’t have lying around, like onions and potatoes and garlic, and that night I went to work. I started slicing and sauteeing at 5 p.m. I realized I didn’t really know how to slice an onion. Then I realized I didn’t know how to choose the right size cutting board, because the stuff I cut up kept spilling over the edge before I was done. And it turns out I’m completely clueless about garlic. Well, I got everything in the pot in the right amounts and simmering away. The baby woke up in the middle of this and I had to put dinner on hold while I fed and changed him. Then I put him in the Baby Bjorn while I finished putting the soup together and pureeing it all in the blender. By the time the chowder was ready to eat it was past 7:30! I was worn out and starving. Then came the cleanup that, in between tending the little guy, took until 9:45.
My question to all you real cooks out there is this: IS IT WORTH IT? I got to the end of the day and seriously asked myself what I had been thinking when I opened my cookbook and set out for the grocery store. The worst thing was, after all that work, John didn’t even care for the chowder all that much. I liked it, though, and had lots of leftovers for days. But I still wonder if cooking’s worth it. Am I aiming too high? Does anyone have any good or bad stories about cooking for their family?
10 Comments »