I love recipes. I just do not think a recipe is the same thing as understanding.
A recipe tells you what worked under one set of conditions. A mechanism helps you recover when your conditions are different.
Your kitchen is not my kitchen
Your oven may run hot. Your refrigerator may run cold. Your flour may absorb water differently. Your room may be ten degrees warmer than mine.
If all I give you is a list of numbers, the moment reality moves away from those numbers you are stuck.
Heat explains the bake
If you understand that the baking surface is delivering energy into the bottom of the pizza, you can reason about preheating, rack position, surface choice, and recovery.
Fermentation explains the dough
If you understand that yeast activity changes with time and temperature, you can adjust when a dough is moving faster or slower than a recipe predicted.
Gluten explains the handling
If you understand that mixing, resting, hydration, and fermentation affect the dough structure, you can diagnose why it tears or springs back instead of simply adding more flour.
Mechanisms create confident cooks
The goal is not to make everybody cook exactly like me.
The goal is to give people enough understanding that they can look at a problem and make a reasonable next decision.
That is also how I think about product education. If you understand why the tool exists and what physical problem it solves, you can use it much better than if I only tell you where to put it in the oven.
