Why I Wrote Diagnostic Kitchen

Most cooking advice is good at telling you what to do — the temperature, the time, the order of things — and for a great deal of cooking, that's really all you need. But it tends to go quiet at the exact moment you'd most like a hand: when something hasn't gone quite the way you hoped. The sauce separates, the fish sticks, the custard turns grainy, the garlic slips over into bitter — and the recipe that brought you this far doesn't have much to say about what to do next. That's usually where the guessing begins, and guessing often means starting over.

I've spent a long time writing recipes, and along the way I kept noticing something gentle and persistent. The cooks I admire most aren't the ones who've memorized the most recipes. They're the ones who can read a failure — who taste a soup that's fallen a little flat and sense it wants some acid rather than more salt, or see a skin that browned too quickly and understand the pan was simply too hot. That isn't magic, and I don't think it's something you're born with. It's a feel you build slowly, over a lot of small and forgivable mistakes.

And if it can be built, it can be shared. That has always been the quiet idea behind this site, and it's why I finally wanted to gather it into a book.

Diagnostic Kitchen grew out of a pattern I kept seeing in my own notes. Looking back over the recipes I'd written, the failures weren't random — they tended to gather into small families. The same handful of mistakes kept turning up in different dishes, just wearing different clothes. A broken beurre blanc and a split mayonnaise are really the same thing. Rubbery scrambled eggs and a grainy custard are, too. Once you notice the shape underneath, a great many separate worries soften into a much smaller set of causes — and each one comes with something easy to check, and something gentle to try next.

So instead of arranging everything by dish, I arranged it by symptom. The book gathers seventy-four of the problems that genuinely come up in home kitchens — the everyday ones, not the exotic ones — and for each it tries to do three simple things. It offers the likely causes, roughly in the order worth considering. It suggests what to check, so you can tell which one is actually yours. And it offers what to try next, so your next attempt feels like a small adjustment rather than another leap in the dark.

The one thing I tried hard not to do was rush to a single answer. Most problems have more than one possible cause, and it felt kinder, and more honest, to lay them side by side and let you narrow things down than to pretend there's always one culprit. My hope is that, little by little, the recipe comes to feel like a friendly starting point rather than something to anxiously obey.

I called it Diagnostic Kitchen because that word felt right — though I mean it warmly. A thoughtful doctor doesn't guess at a fever; they listen to the symptom, weigh the causes, and check before deciding. Cooking can be met with that same calm attention. The stakes are so much smaller and the pleasure so much greater, but the habit of looking before acting is the same, and it's very learnable.

If you've read some of the essays here — why a cold pan won't brown, why high heat isn't always faster, or why a flat dish often wants a little acid rather than more salt — you already hold a few pieces of it. The book is simply where those pieces come together into something you can carry to any dish, even the ones I never wrote a recipe for. That was the hope all along: not to hand you one more recipe, but to help you become the kind of cook who feels at ease needing fewer of them.