Chapter 39 — Exercises

This is a capstone chapter, and the labs are capstone-shaped. Each one is generative — you are not following a recipe; you are designing one. You will make at least one mistake. The mistake is the data. Take notes.

The labs build on each other. Lab 1 walks you through the simplest possible designed dish (a vinaigrette), where the four flavor levers are visible and the chemistry is immediate. Lab 2 asks you to reverse-engineer a dish you love. Lab 3 asks you to adapt a recipe for a dietary restriction. By the end you will have written, cooked, and eaten three recipes that did not exist before you started.

A note on time. None of these labs need to happen in one sitting. Lab 1 can be done in twenty minutes. Lab 2 can take a few weekends. Lab 3 is best done with the friend or family member whose restriction you are designing for, and is therefore as long as a shared meal.

🍳 Lab 1 — Design a vinaigrette from first principles

The vinaigrette is the cleanest possible test of the salt-fat-acid framework. You can hold every variable in your head. You can taste each lever turn at a time. By the end of an hour, you will have either internalized the framework or learned which lever you have been ignoring.

Time: 30–45 minutes for the experiment; another 15 minutes to write down what you learned. Materials: - 1 cup (240 mL) extra-virgin olive oil - 1/4 cup (60 mL) of three different acids — pick three from this list: red wine vinegar, apple cider vinegar, balsamic vinegar, lemon juice, lime juice, rice vinegar, sherry vinegar - 1/4 teaspoon (~1.5 g) fine sea salt, plus more to taste - 1 teaspoon (5 mL) honey OR maple syrup OR sugar - 1 teaspoon (5 g) Dijon mustard (optional but recommended — see the science note) - 1 small shallot, finely minced (or 1 garlic clove, very finely minced) - A small whisk and a 1-cup (240 mL) jar with a lid for shaking - A bowl of mixed greens, or a few leaves of romaine, or some cut tomatoes — any vehicle to taste the vinaigrette on - Six small bowls or ramekins to hold variations Allergens / safety: - ⚠️ Mustard is a common allergen in some regions. If avoiding, omit and follow the no-emulsifier branch. - ⚠️ Raw garlic if pregnant immunocompromised etc. — standard guidance applies.

Protocol.

1. The base 3-1 vinaigrette. Make the classic ratio first, as your reference: in a jar, combine 3 parts olive oil to 1 part of one of your chosen acids — say, 60 mL olive oil and 20 mL red wine vinegar. Add 1/8 teaspoon (~0.7 g) salt. Shake hard. Taste a teaspoon on a leaf of greens. Note: which lever wants to move? Most home cooks find the 3:1 base under-salted on first taste.

2. The lever sweep — the central exercise. Make six small (1 tablespoon / 15 mL each) variations in the small bowls, each varying one lever from the base.

• A: Reference. 1 tbsp 3:1 base.
• B: More salt. 1 tbsp base + 1 small additional pinch of salt (about 1/16 tsp, 0.4 g).
• C: More acid. 1 tbsp base + 1/4 tsp (1.25 mL) more acid.
• D: Less acid. 1 tbsp of a freshly mixed 4:1 oil-to-acid version.
• E: With sweet. 1 tbsp base + 1/4 tsp (1.25 mL) of your sweetener.
• F: Different acid. 1 tbsp of a freshly mixed 3:1 with a different acid (e.g., balsamic instead of red wine vinegar).

Taste each on a leaf of the same greens. Use a fresh leaf each time so palette doesn't muddle. Take one minute between each. Note which one you prefer and why.

3. The full design. Now build a vinaigrette you actually like, using everything you learned. Write it down with measurements. Suggested workflow: pick the acid you preferred. Match the oil at 3:1, 2.5:1, or 4:1 depending on your preference for richness vs sharpness. Salt aggressively and taste. Add a pinch of sweet only if the dish wants rounding. Add the mustard (1/4–1/2 teaspoon for a 1/2-cup vinaigrette) — see science note below — and the minced shallot or garlic. Shake hard or whisk to emulsify. Taste again.

4. Test on something other than greens. Drizzle a teaspoon over a slice of ripe tomato; over a piece of grilled bread; over a quarter avocado; over a bite of cheese. Notice how the same vinaigrette tastes different against different bases. Some pairings will surprise you (a heavily acidic vinaigrette on a fatty avocado is harmonious; the same vinaigrette on greens may feel sharp).

Expected results. Sample B (more salt) is the variation most home cooks gravitate toward — confirming the chapter's claim that under-salting is the most common flavor problem. Samples C and E often pull the vinaigrette in surprising directions; you will probably find one of them is your aesthetic preference. Sample F shows that swapping acid is not a 1-for-1 trade — different acids carry different aromatic accompaniments and pair differently with the oil's notes.

Troubleshooting. - Vinaigrette separates immediately. You did not emulsify, or the mustard quantity is too low. Add more mustard, or whisk more aggressively, or use a small jar with a tight lid and shake hard for 30 seconds. The mustard's mucilage and the whisking together create a temporary emulsion that holds for several minutes — long enough to dress a salad. - Tastes flat even after salt and acid are right. The dish may need umami. Try adding 1/2 teaspoon (2.5 g) of finely grated parmesan, or a few drops of soy sauce, or a single anchovy mashed in. (This is the classic "Caesar move" — the original anchovies are doing umami work.) - Tastes harsh. Add the sweetener in small increments. Or switch to a less-aggressive acid (rice vinegar instead of red wine vinegar, or lime instead of lemon).

🔬 Science note: why mustard works. Mustard contains mucilage, a polysaccharide that acts as a stabilizer in emulsions. The proteins in mustard powder also help. A mustard-stabilized vinaigrette can stay emulsified for an hour or more; a mustard-free vinaigrette typically separates in five minutes. This is not the only emulsifier you can use — egg yolk (lecithin) is the classic mayonnaise-and-Caesar emulsifier; honey can help slightly; pureed roasted garlic adds emulsifying proteins along with flavor — but mustard is the most accessible and the most reliable.

🍳 Lab 2 — Reverse-engineer a beloved dish

This is the central capstone exercise. Pick a dish you love that you do not know how to make.

Time: Several days, spread over 2–4 cooking sessions. Materials: Whatever the dish requires. A digital scale, a notebook, a thermometer, and (ideally) the ability to taste the original at the same time as the version you are building. Allergens / safety: Depends on the dish. Allergen-flag your final recipe.

Protocol.

1. Before you cook, taste with intent. Order or eat the dish at least once with this exercise in mind. Do not just enjoy it. Taste each component. Try to identify, for each component, what it is doing in the dish — what flavor lever it pulls, what textural role it plays, what color it adds. Take notes during or immediately after the meal. If you can, photograph the plate.

2. Sketch the dish on paper. What is the structural backbone? (Soup, braise, sauté, roast-and-sauce, grain-with-toppings?) What are the major components? For each component, what is its role — flavor base, body, finish, garnish?

3. List every ingredient you can identify. Be honest about which you are guessing. Note what each ingredient is doing. (E.g., for a Thai green curry: coconut milk = fat + body + cooling counter to chiles; lime = acid + brightness; fish sauce = salt + umami; palm sugar = sweet rounding; basil at end = aromatic top-note + green color; chiles + galangal + lemongrass + cilantro root = the curry-paste aromatic backbone.)

4. Form a hypothesis recipe. Write down quantities. If you do not know, guess from the visible proportions in the dish. Write the hypothesis in the same form Maya used: ingredients, baker's-percentage proportions if relevant, technique with temperatures and times.

5. Cook the hypothesis. Take notes during cooking. What did you adjust on the fly? What surprised you? What would you change next time?

6. Compare your version to the original — ideally side by side, at least mentally. Where is yours close? Where is it off? Don't aim for replication; aim for understanding why yours is different. Sometimes the answer is a specific ingredient you did not have. Sometimes it is technique. Sometimes it is the time the original was simmered. Sometimes it is the texture of the cut, the size of the dice, the heat the cook used.

7. Iterate. Cook the dish a second and third time. Each time, change one variable. Write down what you changed and what happened.

Expected results. By the third cook, your version will be 80–90% of the way to the original — and will be your version, not a copy. You will have a written-down recipe in your notebook. You will know which variables matter most. You will have a working theory of how the dish builds, and that theory will transfer to other dishes in the same tradition.

Troubleshooting.

• Cannot identify a key flavor. Eat the original again. Try to taste each component in isolation if possible (request the sauce or the side as a separate item). If you still cannot identify, ask the cook — most cooks will tell you a closely-held secret if you say I love this dish and am trying to learn it. Cooks who love their food love when others want to learn.
• The dish is from a tradition you are not part of. See the chapter's section on cultural humility. Cite the dish by its real name, name the cuisine, name the cook (where you can), and consider whether what you are making is the dish or your version inspired by the dish. Both are legitimate; conflating them is not.
• The third cook is not better than the first. You may have changed too many variables. Go back to the second-cook recipe, change exactly one thing this time, and see what that variable does. The whole point of iteration is to learn what each variable contributes.

🍳 Lab 3 — Adapt a recipe for a dietary restriction

Pick a recipe you love. Pick a friend, family member, or invented persona with a dietary restriction (vegetarian, vegan, gluten-free, dairy-free, nut-free, kosher, halal, low-FODMAP, low-sodium, diabetic-friendly). Design a version of your recipe that works for the restriction, using the chapter's substitution principles.

Time: One cooking session of 1–2 hours. Materials: As required by the recipe and substitutions. Allergens / safety: Triple-check the substitutions for cross-contamination. ⚠️ For severe allergies, surface and equipment cross-contamination matters. Gluten-free for someone with celiac means pots, utensils, and cutting boards that have not touched wheat. Nut allergies similarly. Be careful.

Protocol.

1. Decompose the original recipe by function. For each ingredient, write down: what is this doing in the dish? Categories: flavor lever (salt, fat, acid, heat, umami, sweet, bitter), structural function (binding, leavening, aerating, emulsifying, gelatinizing, coagulating), textural function (crunch, cream, chew, slip), or aromatic function (top-note, base-note, ferment-character).

2. Identify the restricted ingredients. Mark each one. For each, note the function(s) you wrote down in step 1.

3. Find a substitute for each function. Use the chapter's substitution principles. Sometimes one ingredient does several jobs and you will need several substitutes. (Eggs are the classic example — you may need flax-egg for binding, baking powder bumped up for leavening, and oil for richness, all replacing the single egg.)

4. Make the substituted recipe. Cook it. Taste critically. Compare to the original (in memory or in fact). Where did the substitution succeed? Where did it fall short? What would you do differently?

5. Cook it for the friend or family member. Their feedback is the data point that matters most. (And cooking for someone with a restriction, when you've thought about it carefully, is a form of care that lands.)

Expected results. Most savory recipes adapt cleanly; baked goods are harder. The hardest categories are: (a) gluten-free yeasted bread (gluten is genuinely irreplaceable for the same texture; the best gluten-free breads are designed gluten-free from the start, not converted), (b) vegan baking that depends heavily on egg structure, and (c) any dish where an aged dairy cheese is the central flavor (vegan substitutes are improving but not yet equivalent).

Troubleshooting. If the substitution does not work, ask: did I match the function, or just the name? "Soy milk for cow milk" matches the name of "milk" but soy milk has different protein, different sugar, different fat content, and behaves differently in baking. "Coconut cream for heavy cream" matches some functions (richness, body) but not others (the dairy proteins that contribute to certain cheese sauces). Function-matching, not name-matching, is the principle.

🍳 Lab 4 (Optional / advanced) — A multi-course meal designed from constraints

For the ambitious. Plan a multi-course meal — three to four courses — built around a constraint set of your choosing. Examples:

• Three courses, each anchored on a different lever. Course 1: high-acid forward (a bright salad or crudo). Course 2: umami-forward (a stew or a pasta with deeply built sauce). Course 3: bittersweet (chocolate, coffee, or caramel-based).
• Three courses, each from a different cuisine, but using a single ingredient as the through-line. Tomato through Italian, Mexican, and Korean — three preparations.
• Three courses for a full table of guests with varied dietary restrictions. Design each course to work for everyone at the table.

Use every tool from the chapter. Salt-fat-acid-heat. Texture contrast. Color framework. Substitution. Scaling. Equipment. Take notes throughout. Photograph the plates. After the meal, write a short retrospective: which design choices worked? Which would you change?

This is the final exercise of the chapter and arguably of the book. The ability to design a multi-course meal on purpose is the cook's analog of the writer's ability to write a novel. It requires holding a great deal of structure in mind at once, balancing many variables, and trusting your taste. By the time you can do it, you have the framework.

Discussion questions

1. Salt-fat-acid-heat: is the framework complete? The chapter argues that the four-element framework is a starting point, not the whole story, and adds umami, sweet, and bitter. (a) Are these seven sufficient? What might be missing? (b) Some sensory scientists argue that fat itself is a sixth taste; others disagree. What would the implications be for the framework if fat were a taste rather than a sensation?

2. The cultural-pairing question. The chapter notes that Western cuisines tend to favor pairings that share many volatile compounds, while East Asian cuisines tend to favor pairings on a "contrast" rather than "harmony" principle. (a) What does this tell us about the universality of the molecular pairing principle? (b) If you grew up eating one of these patterns, can you identify a pairing from your tradition that does not follow the molecular pairing logic? What makes it work?

3. Reverse-engineering ethically. You eat a dish at a friend's house — a dish from their family tradition, not yours — and you love it. You would like to make it at home. (a) Is it appropriate to ask for the recipe? Why or why not? (b) If you make it at home, is it appropriate to share it on social media? To put it on your blog? To call it by its traditional name? (c) Where is the line between learning from a tradition and appropriating from it?

4. The substitution by function principle. Name three ingredients that perform multiple functions in a recipe (the chapter lists eggs as one). For each, list the functions and propose substitutions for each function separately. Where does the multi-function nature make full substitution impossible?

5. Scaling. Why does cooking time not scale linearly with recipe size? Walk through the geometric reason (surface-to-volume ratio). What other variables in cooking scale non-linearly?

6. Equipment as variable. Take a recipe you cook often. Identify three or four specific pieces of equipment it assumes (a pan size, a heat source, a specific tool). For each, ask: how would the recipe need to change if the equipment were substituted? What does this say about whether a recipe is portable to other kitchens?

7. The Aroon principle. Aroon's distinction between technique (mine, transferable) and tradition (not mine to change) is one cook's working ethic. (a) Do you agree with the distinction? (b) Where is it hard to apply? (c) Is there a similar distinction you can articulate from your own cooking history?

8. Pat's classroom assignment. Pat assigns her students a flavor-balance constraint and asks them to design a dish from it. What are the pedagogical strengths of this assignment? What might a critic say is its weakness? How would you redesign it for a different audience (e.g., college students, professional cooks in training, an after-school program)?

9. The cookbook becomes optional. The chapter argues that, with the framework, the cookbook becomes one input among many rather than the source of authority. (a) Do you experience this with cookbooks? (b) Can you point to a specific moment when your relationship to a cookbook shifted? (c) Are there cookbooks you still trust as authority — and what makes them different?

10. The Maya arc. Maya's two-year project to write down her mother's jollof rice is the emotional spine of the chapter. (a) What did the project give Maya that her mother's untranscribed recipe did not? (b) What did the writing-down cost? (c) Is there a recipe in your own life — held by a parent, grandparent, friend — that might benefit from this kind of project? What would the project look like for you?

Advanced sidebar expansions

Baker's percentages, beyond bread

We introduced baker's percentages in Chapter 17. The same framework is generalizable to any recipe where one ingredient is the structural backbone and others are proportional to it. Maya used it for jollof rice, with rice as the 100%. You can use it for stews (the body protein as 100%), for pasta dishes (the pasta as 100%), for soups (the liquid as 100%), for sauces (the base liquid as 100%). The framework lets you scale the recipe arbitrarily and lets you adjust one ingredient as a percentage to test variations.

For example, a basic jollof formula in baker's percentages: - Rice (parboiled long-grain): 100% - Tomato base (blended/reduced): 130% - Stock: 200% - Oil (palm or neutral): 8% - Salt: 2% - Aromatics (onion, ginger, scotch bonnet): 15-20%

To make this for two people, scale to 200 g rice. To make for ten, scale to 1 kg. The proportions stay the same. The technique stays the same. The recipe is portable.

The chemometrics frontier

The Yong-Yeol Ahn 2011 Scientific Reports paper on flavor networks is the foundational study of computational flavor pairing. It analyzed 56,498 recipes from three online recipe databases (epicurious.com, allrecipes.com, menupan.com — two American, one Korean) and computed, for each cuisine, the average number of shared volatile compounds between paired ingredients.

The headline finding: North American and Western European cuisines tended to use ingredient pairs that shared more compounds than would be predicted by chance — supporting Heston Blumenthal's "shared compound" hypothesis as a principle for those cuisines. East Asian cuisines (Chinese, Japanese, Korean) and Southern European cuisines tended to use pairs that shared fewer compounds than chance — implying a contrast principle rather than a harmony principle.

The follow-up literature has nuanced this — the result depends on which compounds you weight, on the recipe corpus, on the granularity of ingredient identification — but the broad finding has held up. The implication for recipe design: if you are working in a tradition that follows the contrast principle, the molecular pairing tool may actively mislead you; trust the cultural pairing wisdom of that tradition. If you are working in a tradition that follows the shared-compound principle, the molecular pairing tool is a useful generative complement.

Substitution chemistry: the egg deep dive

Eggs do at least six things in baking. To substitute, you must replace each.

A successful vegan baked good often combines multiple substitutes, because no single replacer covers all six functions. Vegan baking is a recipe-design problem with severe constraints, and the recipes that work are usually designed for the constraint, not converted from egg recipes. The best vegan bakers (Isa Chandra Moskowitz, Bryanna Clark Grogan, Fran Costigan) have developed substitution toolkits over decades.

🥖 Mastery Food Checkpoint

Where this chapter lands for each track.

• Bread track. Chapter 17 introduced baker's percentages; Chapter 39 generalizes them. If you have followed the bread track, you can now do for any bread what you did for sourdough — pick a bread you love, weigh its components, calculate the percentages, vary one variable at a time, write down the version you settle on. The hydration, the salt percentage, the leavening percentage, the fat-and-sugar percentages — these are your design levers. Pull them on purpose.
• Cheese track. Cheese is the most-constrained design space — you cannot just substitute by function in cheese-making, because the microbial dynamics are specific. But cheese as an ingredient is a recipe-design lever. Knowing what umami, fat, salt, and texture each cheese contributes lets you substitute cheeses across recipes (sharp pecorino for Parmigiano in pastas; aged gouda for cheddar in sauces; feta for ricotta salata in salads).
• Chocolate track. Designing a dish around chocolate is a balance problem: bitterness, sweetness, fat richness, and aroma all need balancing. Pat's classroom assignment translates well — "design a dessert that uses chocolate as both a bitter and a sweet element, balanced by acid and salt." The flake of salt on a chocolate truffle. The lime in a chocolate mole. The coffee in a chocolate cake.
• Fermented vegetables track. Fermented vegetables are some of the most powerful design tools in the umami-and-acid columns. A spoonful of sauerkraut juice as a finishing acid. Kimchi as a topping that adds salt, acid, umami, and crunch all at once. Miso whisked into a vinaigrette base. The track gives you a library of finishing ingredients — and the chapter shows you how to wield them.
• Coffee track. Coffee is most often experienced as a beverage rather than as a recipe ingredient, but coffee-as-ingredient (the pinch in chocolate cake, the brewed shot in a chili, the espresso in a meat rub) is a powerful bitter-and-aromatic lever. The same chapter framework applies: what is the coffee doing in the dish? Bitterness, aroma, color, depth? Match that function and you can substitute another bitter source if the coffee isn't available.