Why Recipes Are Not the Same as Cooking
A recipe is a snapshot of one cook's decision in one moment. Cooking is the ability to change the snapshot when the conditions in front of you change.
The first time I worked the line at a small ryotei in Kyoto, the head cook handed me a fish, a knife, and the instruction to make it ready for the grill. He did not hand me a recipe. He did not say how much salt. He did not say how long. When I asked, he looked at me as if I had asked how much air to breathe. "The fish tells you," he said, and walked off to the next station. It took me roughly six months to understand that he had given me a complete answer. The fish in front of me on a given evening was fatter or leaner than the fish from the same supplier the week before. The salt I had on the bench was a different crystal size from the salt at the next station. The humidity in the kitchen, on a wet Kyoto July evening, was not the humidity of a dry October morning. None of those variables were in any recipe anyone had ever written, and all of them mattered. The recipe could not tell me what the fish needed. The fish could.
I think about this often when I read English-language Japanese cookbooks, because the gap between what they instruct and what a Japanese kitchen actually does is wider than most readers realize, and almost none of the gap is malicious. It is a translation problem, but the thing being mistranslated is not vocabulary. It is the relationship between text and cook. The Anglo recipe tradition, crystallized by Fannie Farmer's 1896 Boston Cooking-School Cook Book and its evangelism for level measurement, assumes the reader needs scaffolding — a precise number, a precise time, a precise temperature — because the reader is presumed to be a beginner, possibly alone in their kitchen, with no senior cook leaning over their shoulder. This is a real achievement and I do not want to dismiss it. There are dishes I would not want to attempt the first time without an Anglo-style recipe to lean on. But the scaffolding is not the building. The teaspoon is not the seasoning. The seasoning is the result on the tongue, and the teaspoon is one path toward it among many.
The Japanese kitchen vocabulary points constantly at this distinction. The verb that does most of the actual work in a Japanese recipe is 加減 (kagen), and it does not have a clean English equivalent. It means calibration. It means moment-by-moment correction. 火加減 is the adjustment of heat — the small drop from a roar to a murmur when the bottom of the pot starts to brown faster than the inside is cooking. 塩加減 is the adjustment of salt — taste, correct, taste again, not measure once and walk away. 味加減 is the larger calibration of the whole flavor of the dish toward what it is trying to be. The companion word 適量 (tekiryō), "an appropriate amount," is the most commonly misread instruction in Japanese cookbooks translated into English. It is not vagueness. It is a deliberate instruction: bring this dish, with the ingredients in front of you, on this day, to the amount that tastes right. The number is in the dish, not in the recipe. I have written about this at greater length in How to Read a Recipe Like a Japanese Chef, and that essay is the practical companion to this one.
There is historical reason for the gap. The Japanese cookbook tradition is older than is commonly understood, and it has never assumed a beginner. 料理物語 — Ryori Monogatari, "Tales of Cookery" — was published in 1643. It reads like notes between professionals: ingredients, sequences, intentions, and the occasional warning about what tends to go wrong. The 1785 万宝料理秘密箱, the so-called "egg book," catalogued more than a hundred preparations of a single ingredient and assumed the reader already knew how to cook an egg before opening it. 温知集 (Onchi-shū), the early Meiji compilation of Edo-era restaurant practice, was written for cooks who had spent years in a working kitchen and needed proportions and order of operations, not lessons in technique. Across centuries, the tradition assumed apprenticeship. The text supplied what the reader could not supply for themselves — the unfamiliar combinations, the structural sequence, the historical antecedent — and left the rest to the cook's trained mouth.
The apprenticeship model has a name and a shape in Japanese kitchens. A young cook spends years on the small jobs — vegetables, dashi, plating — before being trusted with a knife on fish, and the things they learn in those years are not in any cookbook. They are the visual signature of dashi that has been pulled at the right moment versus the wrong one. The sound of oil that has reached frying temperature versus a half-degree below it. The smell of soy that has been heated past its aromatic peak. The feel of dough that has hydrated correctly. None of this is mystical. It is, again, statistics: thousands of repetitions producing a calibrated set of references against which any single new attempt is judged. The recipe a senior cook eventually writes from this knowledge is necessarily a sketch. The fullness of the dish lives in the calibration, and the calibration cannot be written down except as 加減 and 適量 — which are not gaps in the recipe, but the parts of the recipe that point toward where the cooking actually happens.
The limit of any written recipe, Japanese or otherwise, is that it must assume the reader's ingredients and conditions match the writer's. They almost never do. Salt content varies between brands of soy sauce by a factor of nearly two — a teaspoon of one is meaningfully different from a teaspoon of another. The fat content of a pork shoulder is invisible to the recipe writer in another city. A May tomato is not an August tomato. Kitchen humidity changes how flour absorbs water. A gas burner at one address puts out a different heat than the burner where the recipe was tested. To pretend these variables do not exist, and to specify the dish to the tenth of a gram as if they were stable, is to encode a kind of falsehood that any working cook can feel on the tongue. The Japanese kitchen prefers to be honest about this, and the honesty looks, to an outside reader, like vagueness. It is the opposite. It is precision relocated — from the page to the cook.
This is the gap that Working Without Recipes is trying to make visible, and the gap I think most adult home cooks can cross more easily than they realize. The shift is not technical. It is interpretive. A recipe stops being a contract and becomes a conversation between an absent author and a present cook, with the dish on the bench as the third party in the room. The author has told you what the dish has historically been; the cook has to ask the dish, today, what it needs to become that thing again with the materials at hand. Read this way, Working Without Recipes is less a cookbook in the Anglo sense than a practiced argument about who the cooking actually belongs to. After a year of reading recipes this way, most of the frustration that Anglo cooks feel toward Japanese cooking dissolves, and what remains is the only thing that was ever really being taught: the responsibility, and the freedom, to taste.
