My sister in law writes recipes. She has a recipe column in a newspaper and wrote a few high quality recipe books. I saw them in a bookstore. So she's reasonable successful. Her pieces are charming, her recipes inspiring. The thing is. At a birthday party when I was talking to her, she confessed to me that she never actually tries her recipes. When it's time to do a new piece, she sits down at her computer and makes…
As if I needed more fuel on the fire of my burning hatred for recipe collections. Everyone who is interested in cooking should do themselves a favour and buy a proper cookbook. Something that starts with the basics, and works itself up to full meals. It should have cheat-sheets for basic ways to cook all your staples, here's all the ways you can cook a potato, with times and temperature. Here's all the ways you can s…
I tend to disagree on that one, unless you are particularly experienced, or naturally gifted, measuring tools (timers, scales, thermometers,...) will give you the best results. At least for me, that's the case.
And if you can't follow a recipe to the letter, without knowledge of how things are supposed to feel, it is not a proper recipe. The entire point is to give you consistent results, if I had the intuition, I wouldn't need a recipe.
And even if you are an experienced cook, precise instructions and measurements will give you a better baseline from where you can improvise. Yes, I have an idea on how cook a potato, but unless the recipe tells me how to do it, how do I know how potatoes are supposed to be for that recipe in particular?
So yeah, no matter how good at cooking you are, if you "just follow" a recipe properly and it doesn't work, then the recipe is wrong or incomplete. It is like in programming, 99% of the time, where there is a problem, it comes from the software, not the computer running it. And successful developers don't ask users to fix their bugs, even on open source projects where users have the ability to do it, why should it be different for recipe writers?