Loading
Somebody can cook forty recipes well and still stand in front of an open fridge with no idea what to do with what is in it.
That is not a gap in talent. Recipes are instructions for one dish. Nothing about following them teaches you the shape underneath.
Pick almost any hot savoury dish from almost anywhere.
Something fatty gets hot. Something aromatic softens in it. Spices wake up. The main ingredient goes in. Liquid follows. It cooks down. Something fresh or sour lands on top at the end.
A curry, a stew, a pasta sauce and a stir fry are that same order at different speeds.
You have onion, garlic, cumin, chicken, tinned tomatoes and a lemon.
Put these in order
Ground spices thrown into liquid taste dusty and stay in the background.
The smell of a spice lives in oils inside it, and those dissolve into fat, not water. Thirty seconds in hot oil pulls them out and spreads them through the whole dish.
It is the difference between a curry that smells from the doorway and one that does not.
The writer Michael Ruhlman made this his whole argument. A recipe makes one thing. A ratio makes a family of things.
Salad dressing is roughly three parts oil to one part something sour. Once you hold that, every dressing you will ever meet is a variation, and you never need the recipe again.
Three oil, one vinegar, salt, and something to hold it together.
Swap the vinegar for lemon and it is a Greek salad. Add mustard and it thickens and turns French. Use yoghurt as the binder and it goes creamy. Add honey and it suits bitter leaves.
Same skeleton every time.
Why do professional kitchens prepare every ingredient before cooking starts?
Read the whole recipe before you touch anything.
You are looking for two ambushes. Something that needs hours you do not have. And something you have to do to an ingredient before the step that mentions it.
Both of those are usually buried in the middle of a sentence.
The way to substitute is to ask what the missing thing was doing.
Not what it was. What job it had. Something sour can stand in for something sour. Something sweet and sticky for something sweet and sticky. One crunchy green thing for another crunchy green thing.
A recipe wants white wine to deglaze the pan and you have none. What works best?
People worry about having the wrong kind of pan. The wrong size causes far more trouble.
Too small and the food steams instead of browning. Too big and the liquid boils away before anything has cooked.
One wide pan and one deep pot will make almost everything.
Beginners stir constantly, because stirring feels like cooking.
Browning needs contact and stillness. Every stir lifts the food off the heat. Things that should brown want to be left alone and turned once. Things that should not stick want moving.
Deciding which one you are doing is the skill.
Match the complaint to the move.
Tap one side, then its match
Open it and pick four things, not a dish.
Something with protein. Something green or crunchy. Something starchy. And a direction: sour and fresh, or rich and brown, or hot and sharp.
The direction decides the fat, the spices and the finish. That is genuinely all the deciding there is.
A recipe hides the fact that cooking is a loop, not a line.
Do a thing. Taste it. Decide what it needs. Do that. Taste it again.
A cook without a recipe is not remembering more. They are running that loop out loud, several times, on purpose.
When something works, write two lines on your phone that night. What you did, and what you would change.
This is how a person ends up with dishes of their own. Not from inspiration. From the same thing cooked six times with notes.
Pick one simple dish and make it five times, changing one thing each time.
More heat. Less liquid. A different sour thing at the end.
Five versions of one dish teaches more than five different recipes, because only one thing moved, so you can tell what it did.