Our friend Terry said something to us last week about how culture is like a thumbprint embedded on our souls. Like a lot of things we don't pick or ask for, that thumbprint is predetermined for us when we're born;…
We just enjoyed a two-week trial of Grammarly for proofreading—because everybody can use an extra pair of eyes. Learn more about this online editing service in the footer!
Two days ago on our morning walk, Tim and I put on sweatshirts. Yesterday, I pulled out my boots for the first time since May. Today, the window’s open in the bathroom, and even from the next room over, I can smell the fresh air and feel a cool breeze coming in (the high today in Nashville was 72 degrees). What’s more, down the hall and in the kitchen, the oven is on, and I have a pot filled with root vegetables boiling on the stove. Fall is here, officially and obviously, and I’ve been dressing, eating and, what I’m trying to say, I guess, is enjoying this new season, even when it means summer’s gone.
But before we get too deep in changing leaves, could I get one last hurrah for summer? I hate to say it as a lifelong October lover, but sometimes I’m nostalgic for the season that ends (besides winter). And while I was all set to pack away this late summer squash recipe for next year, our Monday CSA pickup brought a few more of the yellow squash we’ve been seeing the last few weeks. So I thought maybe you wouldn’t mind if I slipped this late summer squash quinoa dish in? You could, of course, swap out the yellow squash with a nice winter one, cubed and roasted with oil until it’s caramelized. You could, also, decide to go elsewhere for a recipe featuring pumpkin or apples. I’ll understand.
For now, here’s a quinoa dish we enjoyed before the temperatures dropped and the days shortened. It’s a reminder of the beauty that was, even as we walk forward into the beauty that is and the kind that is to come.
October brought dark and stormy skies today, which is another way of saying it’s a good time for soup. We made this fiery version out of a heap of roasted vegetables recently, and while the corresponding recipe is posted at the bottom of this post, the truth is that making it is much more about a method than it is about a list of ingredients: roast a bunch of chopped vegetables in oil, simmer them in hot water, pureé, add milk, add seasonings, adjust.
The other truth is that, basically, this is how we cook most days.
See, let’s just say, for the sake of argument, that there are two main ways to approach recipes. (I have to say “for the sake of argument” in case any of those of you who are reading here today are the pesky, exacting sort [of which both Tim and I tend to be] and so, when you hear the words, “there are two main ways to approach recipes,” you can’t help it but your mind immediately begins making a case for why there are, in fact, actually at least six different ways to approach it, not two, and once you’ve realized that, you find it’s hard to hang in there through the rest of the paragraphs, having already deemed this post you’re reading to be written by an unworthy source. Listen, you just put those thoughts on hold a minute and rest easy because, right now, we are just talking about this for the sake of argument. Forehead unfurrowed, we continue.)
So let’s say one person gets a recipe, maybe like the one written in this post for an it’s-a-kick-in-your-pants soup, and she looks at her fridge and sees how her ingredients don’t match up with what’s needed and so, she either (a) saves the idea for another day when she’s able to buy everything listed or (b) abandons it altogether.
At the same time, another person gets the same recipe, understands the rough outline of what’s going on, and instead of following it to the letter, she instead pulls out all the carrots and onions, mushrooms, potatoes and zucchini lurking in her crisping drawers, and, experimenting, applies the same strategy to them.
One person caters to the recipe; the other, gets the recipe catering to her.
What’s the difference? Why is one person line-by-lining it and the other, just seeing instructions as a guide? For me, the biggest difference has been time—that incomparably valuable resource that is usually required to learn to do anything, be it speaking a language, riding a bike or handling basic HTML. Do you relate? Has it been that way for you? For me, cooking has been, and continues to be, all about practice, about trying over and over and over again in new ways and the same ways until, one day, you’re making roasted broccoli the way you drive a car, and you’re barely thinking about the way you’re waiting for the smell of crispy florets to tell you when they’re done. The progression from looking at a potato, thinking, how does this become French fries?, to pulling together a meal on the spot is not overnight, at least not for most of us, but usually, it comes.
In our life, Tim and I usually look in the fridge and opt for what’s easy, zucchini to roast and a salad to toss; leftover soup and garlic-rubbed toast; beets (roasted in the CSA apocalypse 2012) to top with goat cheese and toasted hazelnuts. There are times, of course, when we set to making something finer, something bigger, especially when we’ll be dining with guests, and some meals require more preparation, like soaking quinoa or slow-cooking pot roast or preparing a quiche.
But most nights, in our life, we’re throwing quick meals together—not from great skill but from practice, which is the kind of thing I wished I’d heard more often when I was just beginning and, to be honest, which I wish heard from food bloggers and home cooks and great chefs more often. Like a runner or a football player or a businessman, when it’s go time, we’re all mostly drawing on the years we’ve been trying—the failed frittatas and the terrible pie crusts and the cakes that turned gray.
When they happened, the failures were tragedies, but years later, they’re gifts.