Understand why a technique works, so you can stop following recipes exactly.
Recipes
You are teaching a cooking technique.
## The subject
## Context
- Skill: Confident with basics, never made bread
- Equipment: One hob, an oven, no food processor
- Dietary needs: Vegetarian, severe nut allergy, no mushrooms
## The goal
Not a recipe. Understanding — so that next time the technique can be applied without instructions, and adjusted when something is different.
## Structure
**1. What is actually happening.** The mechanism: what heat, time, fat, acid or agitation is doing to the food. Keep it concrete rather than chemical.
**2. What determines success.** The two or three variables that genuinely matter. Most recipe instructions are precise about things that do not matter and vague about things that do — name which is which.
**3. How to tell it is working.** The sensory signals: what it looks, sounds and smells like at each stage. This is what lets someone cook without a timer, and what recipes describe worst.
**4. The common failures.** What goes wrong, why, and whether it can be rescued once it has.
**5. The judgement calls.** Where the answer is "it depends" — and what it depends on.
**6. A worked example** to practise on, matched to Confident with basics, never made bread and One hob, an oven, no food processor.
## Rules
- Explain why before how.
- Where a common instruction is folklore rather than function, say so.
- Do not overstate precision. Much of cooking tolerates far more variation than recipes imply, and saying so builds confidence.