Seasonal Kitchen
There is a particular kind of Saturday that October produces — cold enough for a sweater, dry enough to leave the windows cracked — that seems designed specifically for cooking something long. Not quickly. Not efficiently. Something that requires checking every forty-five minutes and filling the house with a smell that is in itself the whole point, regardless of what you eventually eat.
I have spent a fair number of Saturdays in this mode. My grandmother called it "putting something on," as in, "I'll just put something on," and then she would disappear into the kitchen for three hours while the house reorganized itself around the smell of whatever she had put on. Apple butter. Beef stew. A pot of beans that had been soaking since Thursday.
The recipes I want to share are not complicated. None of them require equipment beyond what is already in most kitchens. But they all require time — which is to say, they require the willingness to let time be an ingredient rather than an obstacle. If you have that, and an October Saturday, you have everything you need.
Leon Says:
Any recipe that improves with an extra hour is worth making on a day when you have extra hours to spare. October produces exactly those days.
The kind that improves when reheated the next day
The error most people make with beef stew is impatience. They rush the browning, add too much liquid, and end up with something thin and gray. The version worth making starts with a good long sear on dry chuck cut into two-inch pieces — not cubes, pieces — in a Dutch oven with a modest amount of oil and real salt. Brown them in batches so the pan stays hot enough to form a crust. That crust is not aesthetic. It is flavor that has nowhere else to come from.
After the meat, aromatics in the same pot: onion, carrot, celery, a bay leaf, a few sprigs of thyme if you have them. A full can of tomato paste cooked down until it turns brick-red. Wine or beer — a full bottle of something you'd drink — reduced by half before the stock goes in. Then the meat returns, mostly submerged, and the lid goes on at a low oven: 325 degrees, no higher, for three hours minimum.
My grandmother's version, which she never called a recipe
My grandmother made applesauce in the oven, not on the stovetop. She would halve a dozen mixed apples — whatever was in the bowl, usually a combination of sweet and tart, never peeled — add a splash of cider, a cinnamon stick, a strip of lemon peel, and two tablespoons of brown sugar, and roast the whole tray uncovered at 350 degrees for an hour and a half. Then she would run the softened apples through a food mill, skins and all, which removed the skins while keeping their flavor and their color. The result was always pink, which she said was the whole point.
I have made stovetop applesauce. It is faster and perfectly adequate. But the slow-roasted version has a depth and a slight caramelized quality that you cannot achieve in a pot on the stove. The oven does something the burner cannot, which is to say: it waits.
A Sunday project that requires nothing but time
Short ribs are, in my considered opinion, the most forgiving of all braises. They are well-marbled, which means they are difficult to overcook (the fat keeps them moist long past when a lean cut would dry out), and they have a gelatinous quality that makes the braising liquid thicken on its own into something you could serve as a sauce without any additional work. They are also inexpensive, which matters when you are feeding people you like.
The technique is identical to the stew above, but longer and with richer aromatics: mirepoix, a whole head of garlic split in half crosswise, a small can of tomato paste, a full bottle of red wine, and beef stock to cover. Five hours at 300 degrees produces ribs that slip off the bone and a sauce that coats the back of a spoon without any reduction needed. Serve over mashed potatoes, polenta, or — if you happen to have made one — egg noodles.
Start on Friday; eat Sunday
This recipe requires planning. The dried beans soak overnight, the ham hock simmers for most of the morning, and the soup itself is best eaten the day after it is made. Three days from pantry to table. This is either deeply impractical or deeply satisfying, depending entirely on how you feel about the relationship between time and food. Leon's position on this is well established.
A smoked ham hock is inexpensive and widely available. Covered in water with an onion, a bay leaf, and peppercorns, it will produce a profoundly smoky, silky broth over three hours of simmering. You drain the broth, pick the meat off the bone (there is more than you expect), then cook your soaked beans directly in that broth until they are tender and beginning to fall apart at the edges. Finish with a handful of wilted greens — kale, escarole, spinach — and a drizzle of olive oil.
Not all slow recipes require the same category of patience. Here is where each of these falls on the spectrum, which runs from "requires an afternoon" to "requires a long weekend."
For toast, biscuits, or eating with a spoon
Pumpkin butter is not butter. It is a thick, spiced pumpkin spread — the autumn equivalent of apple butter — that is made by cooking canned or fresh pumpkin puree down with brown sugar, cider, cinnamon, ginger, cloves, and nutmeg until it is the consistency of a very thick jam. The process is essentially jam-making without the pectin, which means the reducing stage takes a while and requires occasional stirring, but is otherwise completely undemanding.
The result keeps in the refrigerator for two weeks and freezes indefinitely. It is excellent on toast, on biscuits, on oatmeal, or swirled into yogurt. My neighbor Margaret spreads it on crackers with cream cheese and calls it a party appetizer, which is technically incorrect but practically speaking quite smart.
The overnight version your grandmother probably knew
This last recipe requires the least effort of all, which is an argument for including it. Combine one cup steel-cut oats, four cups water or milk (or a mixture), a pinch of salt, and whatever spices you prefer in a slow cooker before bed. Set it to low. Go to sleep. In the morning — eight to ten hours later — you will wake to a kitchen that smells like the dining hall at a very good boarding school, and a pot of creamy, perfectly cooked oats that required nothing of you except the forethought to start them the night before.
Serve with brown sugar and cream, with sliced apples and walnuts, with dried cranberries and maple syrup. The oats are a canvas; what you put on them is your own business. The point is that they cooked while you slept, which is the most efficient use of the slow-cooking principle I know of: it happened without you, and it is better for having done so.
There is a culinary explanation for why these recipes taste better than their faster counterparts, and it involves collagen, Maillard reactions, evaporation, and flavor compound migration. All of that is accurate and interesting. But the simpler explanation is this: low heat over long time produces something that high heat over short time cannot, which is a gradual reconciliation of all the components. The fat and the liquid and the protein and the vegetables have time to become one thing instead of remaining several things in proximity.
The same principle applies, as it happens, to most things worth having. But that is getting philosophical, and this is a cooking column, and the soup is almost ready.
For technique deep-dives, the Serious Eats Food Lab has rigorous scientific breakdowns of braising, browning, and every other slow-cooking technique mentioned here. And the New York Times Cooking section has an excellent archive of low-and-slow recipes worth bookmarking for the full autumn season.