Two recipes today, because the dish demands it. The winter one: brown some beef in a heavy pot, then build a long soup around it — onion, grated beets, shredded cabbage, carrot, potato, a can of tomatoes, broth to cover — and simmer it low for a couple of hours until the whole thing goes deep red and rich and the beef falls apart. Finish with a splash of vinegar and a lot of dill. Serve it scalding, with a heavy spoon of sour cream melting into the middle and dark bread on the side. The summer one: grate raw or lightly-cooked beets, cover with cold buttermilk or kefir, add diced cucumber, radish, green onion, chopped hard-boiled egg, and a storm of dill, then chill it for hours and serve it cold, almost drinkable, shockingly pink. Same name. Same beet. And they are, in every way that matters at the table, opposite soups — and that opposition is the most interesting thing about the dish, so let me make the case that it’s a feature, not a confusion.

We tend to want a recipe to be one thing. We ask “what is borscht” and expect a stable answer — a picture, a canonical bowl. But borscht refuses. It is hot and it is cold. It is a heavy braised meal you eat against the dark and a light chilled drink you sip against the heat. It is winter survival food and summer relief food, and the only thread connecting the two is a root vegetable and a family of people who needed completely different things from their kitchen in January and July and used the same beet, and the same word, to get both. Borscht isn’t a dish. It’s a strategy — a way of running a beet through a whole year — and it wears one name across two opposite jobs the way a single word can carry opposite meanings depending on the weather around it.

I’ve come to love this about the old peasant foods, and it’s the exact opposite of how restaurants think. A restaurant wants a signature dish: fixed, plated the same way every time, reproducible, itself. That’s a commercial value — consistency you can sell. But a home kitchen, a seasonal kitchen, a kitchen that actually lives somewhere with real winters and real summers, has a different value entirely, which is responsiveness. The dish changes because the year changes and the cook changes with it. The point was never to make The Borscht, the platonic bowl. The point was to keep a family fed and comfortable across a climate that swings seventy degrees, and a food smart enough to become its own opposite when the season flips is a food that has understood the place it lives.

And that seasonal split isn’t a compromise or a dilution — it’s a kind of intelligence we’ve mostly lost. We eat the same things in February and July now, shipped in from wherever it’s currently summer, and in gaining that we quietly gave up the deep old skill of eating with the season instead of against it: the heavy braise when the body wants heat and the light chilled bowl when it wants relief, the same ingredient read two completely different ways by a cook paying attention to what the actual month is asking for. Borscht remembers how to do this. It’s a single dish that still knows the difference between the seasons, and it insists you know it too, because you literally cannot make both versions at the same time of year and have them make sense.

So make both — just not today, not together. Make the heavy red one now if it’s cold where you are, with the beef and the two hours and the sour cream, and make yourself a note to make the cold pink one when the heat comes, and notice, when you finally do, that you’re making “the same soup” and it feels like a different food entirely. That’s not the recipe being unstable. That’s the recipe being alive — bending to the year the way a kitchen is supposed to, refusing to be one fixed thing because the place it comes from was never one fixed thing either. One name, one beet, two opposite comforts. The dish knows something we forgot, which is that the right food depends entirely on what the sky is doing.