Home | Archive

the dignity of recipes

🌿 tags: draft inkhaven updated: , ,

(The indignity of having to follow a recipe)

Recipes are a status thing.

Like most status things, as a good little post-Western thinker, I may begin by thinking in a social frame, but I'll revert to frames of individual power and of first principle as soon as I can and see if I can work my way back.

I imagine that there is a deeper natural governance over the corner of reality I am engaging with than can be mediated by a recipe-writing priest; perhaps that reaching for it will give me true freedom, my little furtherance of the Protestant-ish priesthood of all believers. It appeals to my sense of intellectual status to dream of the True Truth, to posit a space of True Forms underneath the mundane space of This Vegetable, that I can manipulate directly.

This is nonsense. Reality, especially corners of reality that humans tend to encode in recipe form, is too messy for that shit. Knowing the Maillard reaction will not save you from learning every last one of its faces. Your perfectly browned asparagus needs to be green underneath the browning and also cooked all the way through, and someone has to be the first to figure out a way to make both of these things happen; for instance, blanching and then shocking in ice water; a trick that you will later find works for some, but not all, fibrous greens. Your instincts for caramelizing onions will kill you dead when you toughen your tofu a step too far. Your cast iron pan reacts chemically with your food. The starch on your rice is a feature for some rices in some dishes in some cuisines, and in some countries will mean you're ingesting heavy metals, or perhaps just aiming for the texture of glue, if you don't wash it out.

You simply can't generalize from the categories you build in a descriptive frame: every chemical reaction, heat curve, mechanical process, occurs in too many settings, in cacophonous concert with too many confounds.

One therefore must learn to cook in procedural units, not units of principle. Baker's percentages. Rests and rises and ferments. Chunks of method and the settings they apply in. Smell, touch, and taste cues. You learn a control flow, and the conditions are just contingent parts of it.

Disconnecting any given procedure from its specific setting, or pulling free a chunk of it, usually doesn't turn it into a principle; by itself it's unlikely to lead to any valid or general description of reality. A series of steps remains a series of steps, even if you translate it into a statement like "if you do X, then Y, then Z, something happens…" You can reason, experiment, or vary your way into learning statements like this, but you can't get rid of that sequence of action conditionals. That's what the thing you're looking at is – a product of a sequence of actions. An approach. A frame. The procedural unit compresses into smaller information shapes, but those smaller shapes are normative. It's a function, waiting for a scenario to be applied to.

The cognitive skill I call manipulation is about domains that work like this. From the inside, running a complex procedure feels like fluency, like virtuosic performance; generative, unrepeatable, always possessed of quality; converging upon a desirable outcome each time. It doesn't always necessarily guarantee the same outcome, and you don't go about achieving outcomes the same way each time; but there's a common thread one layer up; you're always working in the same ways. A manipulator strives to be resilient to variation in input, gleans feedback and creates generality from variance in output. They want to make everything under any conditions, and they want it all to be good.

The atoms of this class of skill are procedure. Their transmissible units are recipes – little generalized chunks of control flow1.

—

The thing is. When someone tells me what to do, they're telling me what to do.

—

When my grandmother taught me recipes, she showed me how much of a spice to put in using the folds of her fingers as measuring marks. I'm never going to forget how her hands look.

—

I ate with the men, in my grandparents' house. The men ate first, and the women served. When I started to get too interested in learning what was going on in the kitchen – or anyone started to get too interested in teaching me – my mum ushered me out. In this effort she was joined by my grandfather. I wasn't meant to be wasted in there, you see. I was meant to study. The knowledge of cuisine would doom me to the use of it, or so the thinking went.

—

When I first learned how to write C, I remember losing hours – hours – to missing semicolons. I couldn't even see them missing. No syntax highlighting, opaque error messages, and, well, vim. Tears were shed, headaches suffered.

—

Alas for the social brain, the collective mind with which we must contend: when I am trying to learn a procedure, I am subordinating my actions to a perceived Other. There are always two things happening:

It takes a bit of finagling to point to this distinction in words, because most of the words we use for one are puns for the other. See: I'm taking direction, I'm being instructed, I'm learning control.

The trick here is that the pun isn't really separable from the semantics, either. You wouldn't actually tell someone what to do without wanting to tell them what to do. This process, and the standardization thereof, is inseparable from this incentive residue. When Alice tells a recipe to Bob, it's because she's invested in Bob ensuring some outcome. What's her investment? Why is she writing this down?

There: we've found our way to the power dynamics.

—

I both love recipes and hate them. I love the piece of reality that does, somehow, get captured by a baker's percentage. I love how I was taught to cook, measuring powders on my fingers. I hate how they need me to let someone reach into my head.

I love the intimacy of a recipe. I hate many of the contexts in which they come about.

I love the psychotech. I hate most of the mindsets.

—

If a friend were teaching me a recipe, I think I'd find it frightening, from the place my heart comes from for these things. Think about it: the trust required to follow along, to act-as-if-it's-true, when someone says, "if you first do X, then Y, then Z, something beautiful happens…"

And if I were to brave that fear, I suspect I would indeed find that something beautiful happens. Something unsullied by the expectations, the larger context, even though it's born in it and molded by it; something that floats free from my suspended disbelief, holding itself aloft from the place I've set it aloft. The product of mere transmission.

Or, to put it another way: there's a kind of love that suggests that Bob wants me to make good spaghetti arrabbiata because they liked it and want me to taste it too.

For such a violent, codependent, status-obsessed, short-lived species, we've accumulated quite a lot of love to go around. Recipes are everywhere for every conceivable recipe-shaped domain, and in the literary corpus they come to me without expectation. I may be slow in my heart to trust it, but it is trustworthy, in that shivery sort of way that happens when you let yourself touch Big Stuff.

I guess I'm saying that the Best Recipes are tools.

Footnotes:

1

Software is a field that concerns itself primarily with recipes. It tries to express some corner of reality that behaves like procedure, and asks a computer to do some of the work of the application. (See SRE is like stage production for POV in this genre.)