Skip to main content

Why I built Chefitt

Why I built Chefitt: recipes that skip the why leave you stuck when a dish fails. This is the technique-first, numbers-first cooking the site exists for.

Clayton Redmon, founder of ChefittClayton RedmonCulinary Educator
Published Updated 3 min read
FlavorBuilding cooking technique — Why I built Chefitt

I built Chefitt because most recipes never tell you why a step works, and without the why you can't fix a dish when it goes wrong. Every post here explains one technique with real numbers. Not "cook the onions until caramelized," but medium-low heat for 35 to 45 minutes, stirring every 3 to 4 minutes, until they're the color of a dark roasted coffee bean.

A recipe you can't explain is a recipe you can't repair.

The stew that started it

A few years ago I made the same beef stew three or four times from the same recipe. The first was fine and the second was better. The third was worse than the first: dry meat, thin sauce, no depth. I went back to find the mistake, and there wasn't one.

I couldn't explain a single decision in that recipe. Why sear in batches? Why does the wine go in before the stock? Why two hours and not four? I'd run it like a script, so the result depended entirely on the script being right, and nothing carried over to anything else I cooked.

The answers were plain once I read the books that explain things, Harold McGee and J. Kenji López-Alt among them. Crowding the pot drops the temperature, so the meat steams instead of browning. The wine goes in first so it can reduce before the stock dilutes it. Two hours is an estimate, and the real test is a fork that slides into the beef without resistance.

Related: Braising: The Set-and-Forget Method for Restaurant Meat

What restaurant kitchens actually do

I trained in a French brigade kitchen and worked the line, and most restaurant "secrets" are the obvious thing done every single time: salting protein ahead, resting meat, reducing sauces instead of reaching for cornstarch, and tasting for acid before a plate goes out. The line doesn't have better information. It just doesn't skip steps.

Most home cooks can follow a recipe fine. Where they get stuck is recovery: the sauce that broke, the meat that came out gray, the bread that didn't rise. So the posts here read like reference cards built around what went wrong, written for a cook who wants the reason. The smoked chicken internal temperature guide is one example, with every cut and target in one place for someone holding a probe during a stalled cook.

The numbers have limits. A home burner puts out less heat than a restaurant range, and pans and ovens vary, so every clock time here comes with a sensory cue to trust when the two disagree.

Where should you start?

Start with whatever goes wrong most often in your kitchen. If your meat comes out dry or gray, begin with browning and doneness. If food tastes flat no matter how much you salt it, the problem is usually acid. If your sauces never come together, start with the pan sauce.

Some of what's here will be rewritten as I learn more or as a reader flags a correction. Every post commits to specific numbers, so you can check them against your own stove.

If you only read one post first, make it the one about the dish you've cooked most often and still can't explain.

Related: The recipe I rewrite before cooking it

Share this article

More from Chefitt

Keep reading.

The Chefitt Newsletter

Cook with more confidence.

Weekly chef techniques delivered to your inbox. The why behind every method, translated for the home kitchen.

No spam. Unsubscribe anytime.