Spare Spoons Kitchen
Spare Spoons Kitchen · Kitchen Notes

Kitchen Notes

Short, practical notes that don't fit on a single recipe — the why behind a cue. More will land here over time.

Why we weigh in grams

The short version: a kitchen scale is faster, more accurate, and means fewer dishes. Recipes here default to grams — the US cup/spoon measures are still on every page (tap ”US measure”), but the gram weights are the ones to trust.

Cups measure volume, and volume lies for solids. A “cup of flour” can weigh anywhere from about 120 to 150 grams depending on whether you scoop, spoon it in, or sift first — a swing of a quarter, enough to turn tender into tough. A gram is always a gram, so weight is the only way to get the same result twice.

The famous “120 grams” is only half the story. You’ll see one cup of flour called 120 grams all over the internet — that’s the spoon-and-level method (fluff the flour, spoon it lightly into the cup, then level off without packing), and it’s King Arthur’s house standard. Scoop the cup straight down into the bag instead — dip-and-sweep, the way most people actually measure — and the flour compacts to about 140–150 grams. The two biggest American baking authorities don’t even agree because of it: King Arthur calls a cup 120 g, while America’s Test Kitchen calls it 142 g — same flour, different scoop. So if your cup keeps landing near 140 grams, your scale isn’t wrong; you’re just a dip-and-sweeper. Weigh the flour and the whole disagreement disappears.

It's actually less work. Set the bowl on the scale, press tare to zero, add the first ingredient up to its number, tare again, add the next. One bowl, no nested measuring cups to wash, no “half a cup plus two tablespoons” arithmetic — and scaling a recipe up or down is just multiplication.

And it lowers the mental load. This site is built for cooks who find vague recipes hostile, and nothing is vaguer than “a cup, packed.” A number on a scale is unambiguous: one clear target, one motion, nothing to second-guess. That's why precision sits at the heart of how these recipes are written.

None of this is anti-cup. Measuring cups and spoons are still the right tool for plenty of jobs — scooping, and quick measures where a little more or less won't change a thing (a cup of rice to cook, a handful of this into that). They're faster than hauling out the scale for the small stuff. The rule of thumb: weigh when it matters (baking, where a 25% swing wrecks things), and scoop when it doesn't. (A favorite set is in the Tool Kit.)

No scale yet? It's the single best inexpensive upgrade you can make — a basic digital one that tares to zero and switches between grams and ounces is all you need (the Tool Kit has picks at a few prices).

Taste and adjust: salt, fat, acid, heat

The short version: when a dish is technically right but tastes off, it's almost always one of four levers. Bland → salt. Flat or heavy → acid. Thin or harsh → fat. Wrong texture → heat. Taste as you cook, and add the one that's missing.

Something's off — what is it?

A scale gets you the same result twice; it can't tell you what a dish needs when it's almost there. That's what tasting is for — and the chef Samin Nosrat, in Salt, Fat, Acid, Heat, made the case that those four elements govern nearly everything that happens in a pan. Learn to hear which one a dish is asking for and you can fix it on the spot, no recipe required. The precision on this site gets you repeatability; this gets you the rest.

Salt makes food taste more like itself — it doesn't just add "salty," it wakes everything else up. Under-seasoned food reads as boring far more often than it reads as needs salt, so salt is the first thing to reach for when a dish falls flat. Season in layers as you cook, not all at the end. (More on how much, and which salt.)

Fat carries flavor and builds texture — it's a cooking medium, it dissolves flavors water can't, and it's what turns things crisp, silky, or tender. When a dish tastes thin, harsh, or one-note, fat is often what rounds it off: a knob of butter swirled in, a thread of good olive oil, a spoonful of cream.

Acid is the counterweight — a squeeze of lemon, a splash of vinegar, a spoonful of pickle or caper brine. It brightens and cuts richness so a heavy dish doesn't sit flat on the tongue. The goal is balance you feel, not sourness you taste: add it a little at a time until the food perks up.

Heat decides texture more than anything else — a hard sear versus a gentle braise is a heat decision, not an ingredient one. Most "not quite right" texture problems trace back here: a sauce that won't thicken needs more reduction; meat that's tough was rushed, or wants longer and lower; a crust that stayed pale needed a hotter pan.

So, at the stove: taste, and ask which one is missing. Bland? Salt first. Rich or dull? A little acid. Thin or harsh? Fat. Texture wrong? That's heat — now or next time. You'll see a small Taste & adjust box near the bottom of the polished recipes here, listing the specific fixes for that dish — this is the map those boxes point back to.

On texture — what you won't find here

The short version: no shredded coconut, almost no nuts in sweets. Both are purely a texture call — the flavors are welcome, just not the mouthfeel. Add them freely if you love them.

I love the taste of coconut. Coconut milk in a Thai soup or curry is one of my favorite things in a bowl. But put shredded or flaked coconut in front of me — in a cake, a cookie, a topping — and something about the stringy, chewy texture gives me the actual willies. The flavor is there; the mouthfeel is not for me.

Same story with nuts in baked sweets. A brownie with a soggy walnut in it goes straight in the trash. I don't want crunch in my fudge, chunks in my frosting, or bits of anything interrupting the texture of a cookie that's supposed to be smooth. But put those same walnuts in a salad, a stir-fry, or a savory grain bowl and I'm all in. And a cookie made with finely ground nuts — like an almond flour shortbread or a French financier — is a completely different and excellent thing.

The distinction isn't flavor; it's mouthfeel. Texture aversions are extremely common, especially for neurodivergent folks, and they don't need to be justified — they're just real. On this site, they shape what gets published.

What this means practically: you won't find shredded coconut as an ingredient in any recipe here. Nuts in baked goods are rare and flagged when they appear (the brown sugar pecans are the obvious exception — the whole point is the candied crunch). Nuts in savory dishes show up freely.

If you love these things: add them. A handful of toasted walnuts folds into almost any brownie recipe. Sweetened coconut toasts beautifully on top of a pudding. The recipes are here as a baseline — adjust to your own palate and texture preferences.

Salt is the same by weight — not by volume

The short version: the gram amounts in these recipes are always right, regardless of what salt you use. If you're measuring by volume and using table salt, use about half the amount the recipe says — a teaspoon of table salt is nearly twice as salty as a teaspoon of Diamond Crystal kosher.

Why this matters. Salt is salt chemically — sodium chloride is sodium chloride — so by weight, all salts are equivalent. But volume tells a different story: the shape and size of the crystals affects how densely they pack. Diamond Crystal kosher salt has large, hollow, flaky crystals that pack loosely; Morton's table salt has dense, fine grains that pack tightly. The result: 1 teaspoon Diamond Crystal ≈ ½ teaspoon table salt in terms of actual saltiness.

In numbers. One cup of Diamond Crystal kosher weighs about 142 g. One cup of Morton's table salt weighs about 273 g — nearly double. (Morton's kosher sits in between, at about 218 g/cup.) This is why following a volume salt amount from a restaurant recipe or older cookbook — where the chef was probably reaching for kosher — can leave a dish oversalted if you're shaking in table salt.

These recipes use Diamond Crystal when a volume amount is given. If you're using table salt, start at half the volume amount and taste as you go. If you're using Morton's kosher, start at about two-thirds. The safest habit is to just weigh the salt in grams — then it doesn't matter what kind you have.

Why Diamond Crystal? A few practical reasons. The large, thin, hollow flakes dissolve faster and more evenly than dense table-salt grains — they melt into food instead of sitting on it. They're also easier to feel: when you pick up a pinch, you can sense how much you have, which is how professional cooks develop salt intuition. The flakes are light enough that over- or under-salting by touch is less catastrophic than with fine salt. And because the crystals are so airy, the saltiness hits immediately and clearly — you can taste where you are as you season.

The trade-off: it's harder to find and costs more. Morton's table salt is in every grocery store, and it's perfectly fine — just remember the volume conversion, or weigh in grams and forget about it entirely. Diamond Crystal is increasingly available at larger supermarkets, Whole Foods, and online, but it's not universal. If you can't find it or don't want to pay extra, Morton's kosher salt is a reasonable middle ground (denser than Diamond Crystal but coarser than table salt, at about ¾ the volume).

The Tool Kit has a pocket scale (the Weigh Gram 200 g, about $11) that's perfect for small, precise amounts like salt and yeast.

Seasoned salt is salt — and the label won't tell you how much

The short version: Tony Chachere's, Lawry's, Old Bay and the rest are seasoned salts, not spice blends. Tony's Original is around 85% salt by weight — a tablespoon of it is roughly 10 grams of salt. When a recipe says "1 tbsp Cajun seasoning," it is salting your dinner, and it isn't telling you.

Do the arithmetic yourself — it's on the jar. Tony's lists a ¼ tsp serving at 1.0 g with 347 mg of sodium. Sodium is 39% of salt by weight, so 347 mg of sodium means 0.88 g of salt in a 1.0 g serving. That's not a seasoning with salt in it. That's salt with a little seasoning in it. Any jar will let you run the same sum: divide the sodium (in grams) by 0.4, and compare it to the serving weight. The answer is usually startling.

This isn't a scandal — it's the category. Used as designed, 85% is correct. You're not meant to add Tony's and salt; Tony's is your salt, with spice riding along. Salting a chicken means about 1% of its weight in salt, and the spices you'd want next to that are a fraction of a gram. Lawry's says so in the name. Tony's says "Creole Seasoning," and that's where the trouble starts — the name describes the small half of the jar.

Salt is also what makes the spice usable. Undiluted, the flavour part is so concentrated it's undoseable: our Salt-Free Creole Seasoning — the same blend minus the salt — needs a scant ¾ teaspoon where Tony's takes a tablespoon. Try shaking an eighth of a teaspoon evenly over a chicken; you can't. The salt is a carrier that turns an unshakeable amount into a shakeable one, the same way vanilla needs the alcohol. It's cheap, it never goes stale, and it's identical batch to batch — so there are honest reasons for it beyond the obvious one that salt costs a fraction of what cayenne does.

What it means for you at the stove. If a dish made with a seasoning blend comes out salty, the blend is the first place to look, and adding "more seasoning" for flavour will only dig the hole deeper — flavour and salt are welded together in that jar and you cannot ask for one without the other. Three fixes, in order: use a salt-free blend and salt separately (ours, or Tony's own No Salt version); use low-sodium stock so the blend isn't stacking on top of it; and don't add table salt until you've tasted at the very end, because the sausage, the stock and the canned tomatoes have all been salting the pot behind your back.

None of which makes the shaker bad. It makes it one decision instead of two, which on a low-spoons day is the whole point — see the salt note for why we weigh it in grams either way. Just know which decision you're making.

Chicken doneness: pull it early, let it rest

The short version: for boneless white meat, pull at 145–150°F / 63–66°C and rest — carryover finishes it safely, and it stays juicy. Dark meat and whole birds still go to 175°F.

Most recipes — ours included — tell you to cook chicken to 165°F / 74°C. That's the temperature at which chicken is safe instantly. But it isn't the only safe number, and for boneless white meat it's the wrong target: pull a breast at 165°F, let it rest, and carryover heat climbs it to 175°F or higher — dry, tight, and stringy.

The fix for boneless white meat is to pull it at 145–150°F and let it rest. Safety is a matter of time and temperature, not one magic number: 165°F kills the bacteria on contact, and 145°F does the same job if the meat holds there for about 8–9 minutes — which is just what happens as a thick breast rests and the temperature drifts up. You get meat that's every bit as safe and far juicier.

How to catch it: a fast or leave-in thermometer makes the low pull easy — I use the ThermoMaven. Pull at 145–150°F, tent loosely with foil, and rest 5–10 minutes; the number keeps climbing while it sits.

The exception — dark meat and bone-in pieces. Thighs and drumsticks are best at 175°F / 80°C, where their connective tissue finally turns tender. And when you roast or fry a whole cut-up bird, you cook to the dark-meat target, so the white meat climbs past 145°F — that's the trade-off of cooking mixed pieces. The early-pull trick is for boneless breasts and cutlets cooked on their own, like the Chicken Piccata or the morel-cream seared chicken.

One caution: this time-and-temperature approach is standard and safe, but if you're cooking for someone pregnant, very young, elderly, or immunocompromised, play it safe and cook to 165°F.

Natural vs. Dutch-process cocoa: which, when

The short version: baking soda in the recipe → natural cocoa. Baking powder or no leavener → Dutch-process (or either). Dutch is darker and smoother; natural is brighter and tangier.

The two aren't interchangeable by accident. Natural cocoa is just roasted, ground cocoa — acidic, light reddish-brown, with a sharp, fruity chocolate punch. Dutch-process (a.k.a. alkalized) has been treated with an alkali to neutralize that acidity, which makes it darker, mellower, and smoother — deep, rounded chocolate without the tang.

Why the leavener decides it. Baking soda is a base and needs an acid to react and make lift; in a chocolate batter, that acid is often the natural cocoa itself. Swap in pH-neutral Dutch there and the rise can fall flat. Baking powder already carries its own acid, so it doesn't care which cocoa you use — and recipes with no chemical leavener (frostings, hot cocoa, ice cream, puddings) don't care either. Rule of thumb: soda → natural; powder or no leavener → Dutch, or whichever you like.

So which do you buy? For deep, dark, smooth results — brownies, powder-leavened chocolate cakes, frostings, hot cocoa — reach for Dutch-process. The budget pick is Hershey's Special Dark (it's Dutched, and it's in every grocery baking aisle); the nicer upgrades are Droste or Guittard Cocoa Rouge. For a brighter, old-fashioned chocolate flavor in soda-leavened cakes and cookies, use a natural cocoa like regular Hershey's or Ghirardelli Unsweetened. (Ghirardelli's standard cocoa is natural; their Majestic is the Dutch one.)

The Bunker Brownies use baking powder, so they're a Dutch-process recipe — Hershey's Special Dark, Droste, or Guittard Cocoa Rouge all shine.

Waxy vs. floury potatoes: which, when

The short version: waxy potatoes (red, creamer, fingerling, baby potatoes) hold their shape — use them where the potato needs to stay a piece: potato salad, chowders, stews. Floury potatoes (russets) fluff, absorb, and fall apart — use them where that's the point: mashed, baked, fries. Yukon Gold sits in the middle and does most jobs well.

The difference is starch and moisture. Waxy potatoes are low-starch and high-moisture: their cells hold together when boiled, so they come out of the pot intact, sliceable, and a little dense — which is exactly what you want in a potato salad or a chowder that simmers a while. They don't drink up butter and cream the way a russet does, so they make a heavier, denser mash.

Floury (starchy) potatoes — russets, above all — are the opposite: high starch, low moisture. Their cells swell and separate when cooked, which is why a baked russet is fluffy and a russet mash absorbs butter like it was born for it. The same quality means they dissolve at the edges in a long-simmered soup or braise — a flaw if you wanted pieces, a feature if you want the pot to thicken itself.

Yukon Golds are the peacemaker: medium starch, naturally buttery, creamy rather than fluffy in a mash, and sturdy enough to survive an hour in a braise — which is why the pot roast calls for them. If you keep only one potato in the house, keep this one.

Quick reference: waxy = red potatoes, creamers, fingerlings, baby/new potatoes · middle = Yukon Gold · floury = russets (Idaho baking potatoes).

Which skillet? Cast iron vs. stainless vs. carbon steel vs. nonstick

The short version: stainless is the everyday all-rounder and the one pan that welcomes acidic sauces; cast iron and carbon steel are for a hard sear but hate acid; nonstick is for eggs and easy cleanup, and it wears out.

Cast iron and carbon steel — the searing pans. Nothing holds heat like them, so nothing sears like them. But their slickness comes from seasoning — a thin layer of oil polymerised onto the metal — and acid strips it. Simmer a tomato sauce, deglaze with wine, or finish with lemon in one and you'll dull the seasoning and can pick up a faint metallic taste. Fine for a quick pan sauce; not the pan for a long acidic braise. Carbon steel behaves identically to cast iron — lighter and smoother, same searing, same seasoning, same acid rule.

Stainless — the do-everything pan. It's nonreactive, so acid is no problem: tomato, wine, citrus, and vinegar are all welcome. It builds the browned fond that makes a real pan sauce, it's oven- and broiler-safe, and there's no coating to wear out — buy one and it's a pan for life. Its one quirk is sticking, and the fix is heat: get the empty pan properly hot before the oil and the food go in, and a good sear releases on its own. (It's the same lesson as searing chicken thighs.)

Nonstick — for eggs and low-energy days. Unbeatable for eggs, delicate fish, and fast cleanup on a day when you've barely got the energy to cook, let alone scrub. The honest catch: every coating wears out over a few years and can't take high heat or metal tools. Keep one for gentle cooking; don't lean on it for searing — which is why a lot of us drift toward stainless and iron for everything else.

Seasoning cast iron or carbon steel is the same process for both, and it's far easier watched than read. Helen Rennie is meticulous and exactly right — her cooking channel has the how-to (she works in carbon steel, but the technique is identical for cast iron).

Garlic: fresh, frozen, jarred, powdered — which, when

The short version: if peeling and mincing garlic is the thing standing between you and dinner, buy Dorot Gardens Crushed Garlic — a tray of frozen cubes in the freezer aisle, one cube = one clove. Drop it in frozen. It's better than jarred and close enough to fresh in anything that gets cooked. Keep fresh heads for the recipes where the garlic stays raw.

Why frozen beats jarred — it's the processing, not the freezing. Garlic has no flavour until you break it: crushing lets an enzyme (alliinase) meet an amino acid, and the reaction makes allicin, which is what garlic actually tastes like. Jarred garlic is pasteurised — the heat deactivates that enzyme, so the allicin never fully develops — and it's packed in citric acid, which adds a sour note that isn't garlic at all. That's the flat, faintly tangy thing you can taste in a jar. Frozen crushed garlic skips both: it's peeled, crushed, and flash-frozen with no heat and no acid. Dorot freezes theirs within about 90 minutes of harvest. It's not fresh garlic, but it's much nearer to it than the jar is.

Where to find it, and what you get. Freezer aisle, near the frozen vegetables — Trader Joe's, Walmart, Kroger, H-E-B, Safeway. A tray is about 16 cubes for around two dollars, each cube a level teaspoon (about 3 g), which is exactly one average clove and exactly what this site means when it writes "3 g garlic — about 1 clove." They go in straight from the freezer and melt in a hot pan in seconds. The tray keeps up to two years, so there's no race to use it.

Here's mine. I hate peeling and mincing garlic. I drop two buttons of Dorot straight into the chicken thigh marinade instead of mincing two cloves, and I've never once missed the difference. It's the single swap that's saved me the most standing at a cutting board.

Where fresh still earns its keep. If the garlic never gets cooked, it is the dish, and any shortcut shows: gremolata, pesto, guacamole, raw tomato and basil pasta, compound butter, a Caesar. Buy a head for those. A frozen cube is still a respectable second there — it's raw garlic, so the allicin is real — but you'll notice it's a little softer and less perfumed. Jarred is the one you'll actually taste, because the sour note has nowhere to hide in a raw dish. Everywhere else — anything braised, simmered, roasted, or fried, which is most of this site — the cube disappears and nobody can tell.

Garlic powder isn't a substitute — it's a different ingredient. It's dehydrated and ground, so it brings a toasty, savoury note rather than garlic's sharp bite, and it can't be swapped one-for-one with anything above. What it's genuinely right for is dry mixes, where a wet ingredient would ruin the blend — a rub, or a Creole seasoning. Just don't buy garlic salt thinking it's garlic powder; it's mostly salt (see the seasoned-salt note for how to check).

Quick reference: anything cooked → a frozen cube is as good as fresh for a tenth of the work · raw dishes → fresh is worth it; frozen is a fair second · dry rubs and spice blends → powder · jarred → it'll survive a long braise, but the frozen tray costs about the same and is better everywhere, so there's not much reason to keep buying it.

Is organic worth it? A practical guide

The short version: buy organic for thin-skinned produce you eat whole — especially anything on the Dirty Dozen list. Skip it for thick-skinned fruits and vegetables where you discard the peel. For dairy and eggs, organic is worth it if your budget allows.

Organic matters most for produce where pesticide residues end up on the part you actually eat. Thick-skinned fruits and vegetables act as a natural barrier, so the premium isn't worth it there. Beyond produce, animal products are worth considering because animals concentrate whatever was in their feed.

The best tool for navigating this is the EWG Shopper's Guide to Pesticides in Produce, updated every spring at ewg.org/foodnews. A note: some food scientists think EWG overstates the risk from conventional produce, since residue levels still fall below regulatory limits. But if you're going to prioritize organic anywhere, the Dirty Dozen is where it makes the most difference.

Buy organic when you can — the 2026 Dirty Dozen. 96% of samples tested positive for pesticide residues. PFAS (“forever chemicals”) were detected on 63% of Dirty Dozen samples.

Spinach · Kale, collard & mustard greens · Strawberries · Grapes · Peaches · Nectarines · Apples · Cherries · Blueberries · Blackberries · Pears · Potatoes

Conventional is fine — the 2026 Clean Fifteen. Nearly 60% of samples had no detectable pesticide residues at all.

Avocados · Sweet corn · Pineapple · Onions · Papaya · Frozen sweet peas · Asparagus · Cabbage · Cauliflower · Watermelon · Mangoes · Bananas · Carrots · Mushrooms · Kiwi

Beyond produce. Dairy and eggs are worth buying organic if your budget allows — not because of direct pesticide residue, but because animals concentrate what they ate. Organic dairy and eggs come from animals on organic feed grown without synthetic pesticides. If you have to choose one, eggs are the easiest organic swap and usually the smallest price jump.