Why cooking works

Dry the meat. Not a token dab — take a piece of kitchen paper and press until it stops coming away wet.

That one instruction carries most of the chemistry in this article, and almost no recipe bothers to say why it's there. Recipes are written as orders. Rest the meat. Don't crowd the pan. Salt the water. Every one of them is sound, and every one is a chemical process wearing an apron.

There are far fewer of these processes than the length of an average cookbook implies. Browning, protein coagulation, starch gelatinisation, collagen breakdown, emulsion, pectin and acid account for nearly everything that happens between a raw ingredient and a plate. Learn the half-dozen and the rules stop being arbitrary — you can bend them, and, more usefully, you can work out what went wrong when something fails.

Browning is two different reactions, not one

People use browning as though it were a single thing. It isn't, and the difference matters more than most kitchen distinctions.

The big one is the Maillard reaction, named after Louis-Camille Maillard, the French physician and chemist who published on it in nineteen twelve. It needs two ingredients: amino acids, which come from protein, and reducing sugars. Heat them together above roughly a hundred and forty degrees Celsius and they start a cascade that doesn't stop at one product. It generates hundreds of new compounds — nutty, roasted, meaty, bready — none of which existed in the raw ingredient. That's the gap between boiled chicken and roast chicken, between dough and crust, between a raw onion and a browned one.

Caramelisation is something else entirely. It's sugar alone, breaking down under heat with no protein involved at all, and it needs to get considerably hotter — table sugar doesn't really go until around a hundred and sixty degrees. The flavours it makes are different too: sweeter, more buttery, more obviously burnt-sugar. Both processes turn food brown. Only one of them needs an amino acid, and the two produce recognisably different smells.

Neither of them is burning. Burning is what happens when you keep going past the point where the useful compounds crack apart into bitter ones, and it's a separate event with its own chemistry.

Two odd consequences fall out of this. Table sugar isn't a reducing sugar, so on its own it's a poor Maillard partner until heat splits it into glucose and fructose. And the reaction runs faster in alkaline conditions, which is why a small pinch of bicarbonate of soda will brown a pan of onions in a fraction of the usual time. It's also why that trick makes them taste slightly soapy if you overdo it. The chemistry doesn't care what you intended.

Water sets a ceiling at a hundred degrees

Here's the constraint that governs the whole first half of your cooking.

Liquid water in an open pan can't get past its boiling point. Add heat and it doesn't get hotter, it just evaporates faster. So any surface that's wet is stuck at a hundred degrees, and browning starts about forty degrees above that. A wet surface can't brown. That isn't a preference, it's a temperature ceiling, and no amount of patience gets round it.

Which explains the paper-towel instruction, and it explains the crowded pan. Pile too much into a pan and the food dumps steam faster than the pan can drive it off. The surface sits in its own moisture at boiling point, and you get grey meat and a puddle. Cook the same food in two batches and the same pan produces a crust. Nothing changed except how much water was in the way.

It also explains why boiling, steaming and braising never brown anything, however long you leave them. If a braise tastes deep, something got browned before the liquid went in — that's what the first ten minutes of nearly every stew recipe is for. The brown scraps welded to the pan afterwards are called fond, they're largely water-soluble, and a splash of wine or stock lifts them straight back into the sauce. Deglazing isn't a flourish. It's recovering the best part.

Searing has never sealed anything

The most durable myth in cooking is that a hard sear forms a seal that traps moisture inside the meat.

It came from Justus von Liebig, a genuinely great nineteenth-century chemist who was wrong about this, and it spread because it sounds mechanically plausible. It has been tested many times since by the simple method of weighing the meat. Seared meat loses about as much moisture as unseared meat, and sometimes a little more, because a hot crust keeps driving water off.

Sear anyway. The flavour compounds are the entire point and they're worth the trouble. Just stop believing the crust is a raincoat.

Heat unfolds protein, and then it squeezes

Proteins are long molecules folded into particular shapes. Heat shakes them loose — denaturation — and the unfolded strands then link to one another, which is coagulation. A runny translucent egg becomes an opaque firm one, and nothing you do reverses it.

Different proteins give up at different temperatures, which is why an egg is such a useful teacher. Egg white sets somewhere around sixty-two to sixty-five degrees. The yolk thickens a little above that and sets closer to seventy. Hold an egg at sixty-five for an hour and you get a set yolk in a barely set white, which sounds like a mistake and is actually a well-known restaurant dish.

Meat runs on the same logic. The proteins that make muscle contract start denaturing around fifty degrees, and a second set gives way around sixty-five. Past that point the protein network tightens hard and physically wrings water out of the meat. This is what overcooking is. The moisture didn't evaporate — it was squeezed out and left in the pan, and there's no putting it back.

Resting works for the same reason, and not the reason usually given. During cooking the outer layers contract violently and shove juice toward the middle while pressure builds. Cut into it straight away and that pressure vents onto the board. Leave it a few minutes and the temperature evens out, the contracted proteins relax slightly, and the liquid spreads back through. Nothing is being reabsorbed. It just isn't under pressure any more.

While it rests it also keeps cooking. A large roast can climb several degrees after it comes out of the oven, because the hot outside is still feeding heat into the cooler middle. Pull big things early or you'll overshoot.

Tough cuts want time far more than heat

Muscle that works for a living is strapped together with connective tissue, most of it collagen. Collagen is what makes shin, shoulder and brisket chewy, and it doesn't behave like muscle fibre at all.

Heat it quickly and it contracts, wringing the meat out even harder — which is exactly why a fast-cooked stewing cut is worse than the raw article. Hold it above about seventy degrees for long enough, though, and it slowly unwinds into gelatin. That's the substance that gives a proper stew its body, the thing that makes your lips slightly tacky, and no amount of added fat imitates it.

The conversion depends on time much more than on temperature. That's the whole argument for low and slow, and it's why a recipe that says "or until tender" instead of giving you a number is being honest rather than lazy. It genuinely depends on the animal, its age and how hard that particular muscle worked.

So cuts sort into two groups with opposite rules. Tender ones from lazy muscles want high heat and a short stay, and the only skill is browning the outside before the middle overshoots. Hard-working ones want the reverse, and you can't make up the time later.

Starch is the thing that thickens

Starch granules are packed tight and basically inert until water and heat reach them. Somewhere in the region of fifty-five to seventy degrees, depending on where the starch came from, they take on water, swell and rupture. That's gelatinisation, and the long molecules that spill out tangle with each other and thicken whatever they're sitting in.

Nearly every thickening technique is this same event, managed differently. A roux disperses flour through fat first so the granules can't clump into lumps before they hydrate. A cornflour slurry uses cold liquid for the same reason. Pasta water works because the pasta sheds starch into it, which is why a ladleful pulls a sauce together and makes it cling instead of sliding off the plate.

It sorts out potatoes, too. A floury potato holds more starch and less water, so it collapses into something fluffy — right for baking and mashing, hopeless in a salad where the cubes need to survive. A waxy potato does the opposite. Buying the wrong bag is probably the most common cause of a dish failing for no visible reason.

Vegetables soften for a completely different reason

Meat gets tender when protein and collagen give way. Vegetables have neither, and they soften by a route of their own that's worth knowing because it explains a very specific kitchen failure.

Plant cells are glued to each other with pectin. Cook them and the pectin gradually dissolves, the cells stop gripping, and the vegetable goes soft. That process wants heat and time, like everything else — but it's also slowed down sharply by acid.

Which is why beans simmered in a tomato sauce can sit there for hours refusing to soften while the same beans in plain water are done in one. If a recipe tells you to cook the pulses first and add the tomatoes afterwards, that's not fussiness. Hard water does something similar, because calcium reinforces the pectin.

Acid has one more effect on vegetables, and it goes the other way. Green vegetables owe their colour to chlorophyll, which loses its magnesium atom in acidic conditions and turns a dull olive. A pan of greens dressed with lemon and then left to sit will visibly go drab. Dress them at the table.

Salt is doing three jobs at once

Salt gets treated as one ingredient with one purpose. It has at least three, and they run on different timescales.

The first is taste, and even there it's doing more than tasting salty. Salt suppresses bitterness and lifts the perception of other aromatics, which is why an under-salted dish reads as flat and vague rather than simply unsalted. People reach for more herbs when what's missing is sodium.

The second is water and texture. Salt applied to meat well in advance dissolves into the surface moisture, gets drawn inward, and partially breaks down the muscle proteins so they hold onto water more stubbornly during cooking. That's the whole principle behind brining, and it's why salting an hour ahead is a different operation from salting at the pan.

The third is timing, and here one popular claim is simply false. Salt does raise the boiling point of water, but at kitchen concentrations by something like a fifth of a degree — nowhere near enough to notice, and it certainly doesn't make water boil faster. Salting pasta water is about seasoning the pasta itself, which drinks in that water while it cooks and can't be seasoned as effectively afterwards.

The savoury taste nobody had a name for until nineteen-o-eight

Kikunae Ikeda, a chemist at Tokyo Imperial University, spent years trying to pin down what made kombu broth taste the way it did. In nineteen-o-eight he isolated glutamate and argued it was a basic taste in its own right, separate from sweet, salty, sour and bitter. He called it umami.

Western food science took most of a century to accept that, and it's now uncontroversial: there are receptors on the tongue for glutamate, and they aren't the ones that handle the other four.

What this buys you in a kitchen is a list. Parmesan, anchovies, soy sauce, fish sauce, dried mushrooms, tomato purée, miso and long-aged or long-cooked anything are all heavy in free glutamates. A spoon of any of them added to a dish that tastes thin doesn't announce itself — it makes everything else taste more like itself. That's the effect people are chasing when they say a dish needs "more depth" and can't say what of.

Fat and water, and the things that make them cooperate

Fat and water don't mix, which is awkward, because a great many sauces are exactly that. An emulsion is a suspension of tiny droplets of one held apart inside the other, and what holds them apart is an emulsifier — a molecule with one end that likes water and another that likes fat.

Egg yolk is the classic, because it's full of lecithin, and that's why mayonnaise and hollandaise are built on yolks. Mustard does the same job in a vinaigrette. When a sauce splits, the droplets have found each other and merged back into layers, and it's almost always because the fat went in too fast or the temperature swung too hard. The rescue is to start again with a fresh scrap of emulsifier and dribble the broken mixture back in slowly.

Fat matters for flavour as well, for a reason that's easy to miss: a lot of aroma compounds dissolve in fat and not in water. Strip the fat out of a dish and you haven't only made it less rich, you've thrown away some of the molecules responsible for its smell. Most of what people call taste is smell, so the loss is bigger than it sounds.

Fats also differ in how much heat they'll take before they start smoking and turning acrid. Refined oils generally handle more than unrefined ones. Butter takes the least of all, and not because of the fat — it's the milk solids suspended in it, which scorch long before butterfat is in any trouble. Clarify the butter and the problem goes away entirely. Adding a splash of oil to the butter in a pan is the lazy version of the same fix.

Why a cast-iron pan gets better with age

Seasoning a pan sounds like folklore and is plain chemistry. Thin films of oil heated past their smoke point polymerise — the fat molecules cross-link into a hard, varnish-like layer bonded to the metal. Repeat that enough times and you've grown a non-stick surface rather than bought one.

The care instructions follow directly. Harsh detergent and long soaking attack that polymer. Drying the pan on a hot hob after washing drives off water before it can rust the iron underneath. And a scratch isn't fatal, because you can always grow more.

Cast iron also behaves oddly on the hob, and people misread why. It's actually a mediocre conductor — aluminium moves heat several times better — so it heats unevenly and takes ages to come up. What it has is mass. A heavy pan stores a great deal of energy, so when cold food hits it the surface temperature barely dips, and that's what gives you a crust instead of a grey slick. The same mass is why it punishes you if you walk away from it.

Acid is the fix for most flat food

The commonest fixable fault in home cooking isn't too little salt. It's no acid at all.

Long cooking rounds things off and concentrates them, and past a point everything starts tasting like one heavy note. A squeeze of lemon or a splash of vinegar right at the end cuts back across that. It doesn't make the dish sour if you're sensible about it — it restores contrast that the heat flattened out.

Think of salt, acid and fat as three separate dials. Most of what separates a confident cook from a careful one is diagnosing which dial is short, quickly, from one taste. That's a skill you build by deliberately tasting a dish before and after adding each one, which nobody does, because it feels like homework.

Temperature is the real variable and time is a guess

Nearly every process in this article is defined by a temperature. Maillard above roughly a hundred and forty. Egg white at sixty-odd. Collagen above seventy. Starch in the fifties and sixties. Pectin higher still.

Cooking times, meanwhile, are estimates built on assumptions about your pan, your hob, the starting temperature of the food and the thickness of the piece — and at least two of those are wrong in your kitchen right now. A cheap probe thermometer converts most of this article from theory into something you can actually see happening.

It also explains sous vide, which otherwise looks like a gimmick. Holding food in water at a fixed temperature means the food can't go past it, no matter how long you leave it. You've removed timing from the problem. Water carries heat into food far faster than air does, too, which is why a seventy-degree bath cooks briskly while a seventy-degree oven barely does anything.

Five faults and what they usually mean

• It tastes flat and more salt doesn't help. Almost always missing acid. Lemon, vinegar, or something pickled, added at the very end.
• The meat went grey instead of brown. The surface was wet or the pan was crowded, so it steamed at a hundred degrees and never got near browning temperature.
• The stew is still tough after two hours. Usually not enough time rather than too much. Collagen converts slowly, and the window where a cut is tough before it turns tender can run for hours.
• The sauce split. Fat added too fast or the heat moved too sharply. Start again with a little emulsifier and feed the broken sauce back in slowly.
• The beans never softened. Acid in the pot. Cook them through first, then add the tomatoes.

None of this needs equipment or precision, beyond a thermometer you can buy for the price of a takeaway. It needs you to know what the heat is doing. That turns a recipe from a list of orders into a description of a process you can adjust — and, when it goes wrong, one you can actually diagnose instead of blaming the oven.