The recipe says serves six. There are two of us. It is a Tuesday in early March, and the soup — a white bean and rosemary thing, the kind of soup that takes the same hour whether you cook a pint of it or a gallon — wants two cans of cannellini, a quart of stock, half a head of garlic, a generous pour of olive oil. I stand at the counter with a pencil and a wet hand and divide everything by three, which is the easy part, and then I get to the salt.
Two teaspoons of salt, divided by three, is two-thirds of a teaspoon. I do not own a two-thirds-teaspoon measure. No one does. So I do what every home cook does — I eyeball it, I round down because salt is forgiving in only one direction, and I tell myself I will taste and adjust later. This is the math of cooking for two from a recipe written for six. It is small and it is constant, and over the course of a week of dinners, it is the quiet tax the home cook pays for the assumption — built into nearly every recipe ever published — that you are a household of four.
§ I.The Math Nobody Wrote Down
Recipes default to four because cookbooks default to four. Cookbooks default to four because the postwar American family did, and because four is a number that divides cleanly in two directions — half it for two, double it for eight, and the publisher is covered for most of the population most of the time. The trouble is that the population stopped looking like that some time around 1972 and has kept moving. The average American household is now closer to two and a half people. The recipe still says four.
And so the home cook does the arithmetic. A pound of pasta becomes ten ounces. A cup of cream becomes two-thirds of a cup, which is eleven tablespoons rounded, which is — fine, near enough. Three eggs becomes two and you hope for the best on the binding. A teaspoon of baking soda becomes two-thirds of a teaspoon, which is the kind of measurement that produces, in a small loaf, a slightly denser crumb than the recipe writer intended, and you spend the rest of the afternoon wondering whether it was the soda or the flour or the oven.
None of this is hard, exactly. It is only that it is constant — a low, ambient cognitive cost that compounds across a week, a month, a cooking life.
§ II.Why Doubling a Cake Is Not Doubling a Cake
The arithmetic is the easy part. The harder part is what no recipe tells you at all, which is that doubling does not always work. A cake that bakes in twenty-eight minutes in an eight-inch round will not bake in fifty-six minutes if you double the batter and pour it into the same pan — it will overflow, and the center will still be wet at the hour mark, and the edges will be the colour and texture of an old shoe. You needed a different pan. The recipe did not say.
Leavening does not scale linearly. A teaspoon of baking soda lifts a single-layer cake; two teaspoons in a doubled batter, in a vessel that is twice as tall, will lift it briefly and then collapse it, because the structure cannot hold. Salt scales — until it doesn't, because past a certain mass the perception shifts and what tasted bright at one volume tastes aggressive at three. Yeast scales reliably, but proofing time does not, because a larger mass of dough holds heat differently than a smaller one.
And then there is unit dignity. A quarter teaspoon of cayenne, doubled, is half a teaspoon. Doubled again, it is a teaspoon. Tripled from the original, it is three-quarters of a teaspoon — a measure that exists, technically, but that no one carries. Multiplied by twelve, it is three teaspoons, which any sensible recipe would simply call a tablespoon. The math is correct at every step. The kitchen is the place where the math has to become something a hand can hold.
§ III.What a Recipe App Should Quietly Do
The argument I would like to make is that this is not the cook's problem. Or rather — it is the cook's problem only because the recipe, as a document, has historically been static, printed once, fixed at the size the publisher chose. A recipe on paper cannot know that you are two people instead of four. A recipe on a screen can.
What the screen owes the cook, then, is the boring math, done well — which means not just multiplication, but judgement. It means knowing that two-thirds of a teaspoon is a measurement no one will execute and rounding it to something the kitchen can perform. It means knowing that three teaspoons should be displayed as a tablespoon. It means flagging, when the cook scales a cake from one round to three, that the pan they are reaching for is no longer the right one. None of this is exotic. All of it is missing from most of the apps that promise to help.
Basil's recipe-scaling lives behind a slider — one to twelve — at the top of every recipe card. You drag it. The ingredients update in place. A quarter cup of olive oil scaled to three becomes three-quarters of a cup, which the app shows as three-quarters of a cup and not as twelve tablespoons, because three-quarters of a cup is what the kitchen uses. A teaspoon of salt scaled to twelve becomes a quarter cup, because twelve teaspoons is a quarter cup and the cook reaching for the kosher should know this. The unit moves with the volume. The cook does not have to ask.
Where pan size matters — the cake, the loaf, the gratin — a small note appears under the title: at three times this volume, consider a nine-by-thirteen rather than the eight-inch round. The note does not insist. It is the app saying, gently, that the math has gone past the vessel. You can ignore it. You usually shouldn't.
The math is correct at every step. The kitchen is the place where the math has to become something a hand can hold.
§ IV.The Birthday Cake, Tripled
I tested this on a chocolate cake last month — a recipe I have made perhaps twenty times for two layers, eight inches across, that needed, for a child's birthday, to feed eighteen. Three times the volume. The old way: a notebook page of arithmetic, a recalculation of baking time I would not trust until I had cut into it, a small panic about whether the cake would dome too much in the larger pan and crack across the top.
The new way: I dragged the slider to three. The flour went from a cup and a half to four and a half cups, the sugar from a cup to three, the eggs from two to six, the baking soda from a teaspoon to a tablespoon — which is what the app said, because three teaspoons is a tablespoon, and the app knew. A note appeared: at this volume, a nine-by-thirteen pan, baked in two batches, will produce more even layers than a single deeper pan. I made it in two batches. The layers were even. The cake fed eighteen. The cook had not opened a calculator.
The soup is on the stove. The slider is at one-third. There are two of us, and the salt — two-thirds of a teaspoon, displayed as a half plus a pinch — has already gone in. The pencil is back in the drawer. Outside, it is still March, still Tuesday, still the kind of evening that wants white beans and rosemary and not very much arithmetic. The cake, when its turn comes, will be tripled. The math will be done. The cook, for once, will be free to taste.
