Why I built Chefitt

The honest answer is that I got tired of recipes that don't tell you why anything works.

About four years ago I was making a beef stew for the third or fourth time. I'd followed the same recipe each time. The first time was fine. The second was a little better. The third was somehow worse than the first — meat dry, sauce thin, no depth. I went back to the recipe to find the bug. There wasn't one. I'd done every step exactly. The recipe had nothing left to teach me.

That bothered me more than I expected. I'd spent maybe forty hours total cooking that stew over the years. At the end of it, I couldn't explain a single decision in the recipe. I didn't know why we seared in batches. I didn't know why the wine went in before the stock. I didn't know why the recipe specified two hours and not three or four. I had pattern-matched the recipe like a script and gotten a result that depended entirely on the recipe being correct. The skill never transferred to anything else I cooked.

I started reading the cookbooks that actually explain things. Harold McGee, J. Kenji López-Alt, Madeleine Kamman. CIA technique manuals. The Modernist Cuisine boxset that takes up half a shelf. I read about Maillard reactions and gelatin extraction and the difference between blanching vs. parboiling for what felt like a year. And then I started cooking again, with the same recipes, and everything got better. Not because I'd memorized more recipes. Because for the first time I could explain what was happening in my pan.

That's the gap Chefitt is trying to fill. There is no shortage of recipes on the internet. There is no shortage of cooking content. What's missing is writing that treats technique as a first-class subject — explained in plain language, anchored in real food science, applicable across every dish you'd actually make at home.

When I look at the cooking writing that's worked best for me over the years, it has three things in common. It explains a method, not just a dish. It treats the reader as someone who wants to understand the method, not just execute it. And it commits to specific numbers — temperatures, ratios, times — instead of hedging with "to taste" or "until done." That last one matters more than people think. "Cook until the onions are caramelized" is useless. "Cook over 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" is information you can actually use.

So that's what Chefitt is trying to be. A site where every article explains a single technique, in plain language, with the specific numbers professional kitchens actually run on, anchored in the food science that makes the technique work. No fluff, no marketing voice, no "delicious comfort food perfect for chilly nights" intro copy. Just the methods.

A few things I've learned writing this so far:

First, the methods that home cooks struggle with most are almost never the ones I expected. Most people can follow a recipe. What they can't do is recover from a mistake — the sauce that broke, the meat that came out gray, the bread that didn't rise. The articles I'm proudest of are the ones that explain what went wrong so the reader can fix it next time instead of throwing the dish out and looking for a new recipe.

Second, restaurant kitchens are way less mysterious than they're made out to be. Most "restaurant secrets" turn out to be the obvious thing done with care. Pre-salting protein. Resting meat for as long as it took to cook. Building sauces from real reductions instead of cornstarch. The reason it tastes better at a restaurant isn't because they have access to magic; it's because they don't skip steps. Once you know which steps actually matter, the gap closes fast at home.

Third, the audience I'm writing for is more capable than most cooking content assumes. People who are reading a 2,000-word piece on the chemistry of a pan sauce don't need to be talked down to. They want the actual technique. They want the why. Treating the reader like an apprentice, not a beginner, is the only way this kind of writing works.

If you're new to the site, the pieces I'd start with depend on what frustrates you most in your own kitchen. If meat is the problem — dry, gray, tough, overcooked — start with the resting-and-doneness pieces and work back from there. If your food tastes flat no matter what you do, start with the seasoning and acid pieces, because that's almost always the issue. If your sauces never quite come together, the sauce pillar is where I'd send you.

I'm aware that the site is young and that there's plenty I haven't written about yet. Some of what's here will get rewritten as I learn more or as a reviewer flags a correction. That's the deal. The promise isn't that every article is perfect on day one. It's that every article is honest about what it claims, specific about the numbers it gives, and written by someone who actually cooked the thing and wrote down what they learned.

If you want technique writing that respects your time and your intelligence — welcome. I built this site for you.

— C.R.