![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Bad recipe! No biscuit!
Feb. 4th, 2009 03:00 pm...Or at least, badly cooked biscuits.
Writing recipes is not a form of writing I usually think much about, except when it's done badly. Here is your forum for complaining of recipe-writing errors, confusions, or just general weirdness. The two examples that come to mind from my own experience are:
1) A recipe for Greek meatballs, which called for a couple of fresh tomatoes, "shredded." How, I ask you, do you shred a fresh tomato? (The sad thing was, I actually tried. Don't. Just don't, ever.)
2) Recipes that wait until the last line to tell you something that would have been best to know in the early stages. For instance, a buffalo wings recipe I used recently included the recipe for the sauce, of course, and listed those steps after the whole chicken preparation part. That'd be fine, except the last line? "Cover and chill [sauce] for 2 to 4 hours." Would've been good to know two to four hours ago, thanks.
What are your recipe complaints?
Writing recipes is not a form of writing I usually think much about, except when it's done badly. Here is your forum for complaining of recipe-writing errors, confusions, or just general weirdness. The two examples that come to mind from my own experience are:
1) A recipe for Greek meatballs, which called for a couple of fresh tomatoes, "shredded." How, I ask you, do you shred a fresh tomato? (The sad thing was, I actually tried. Don't. Just don't, ever.)
2) Recipes that wait until the last line to tell you something that would have been best to know in the early stages. For instance, a buffalo wings recipe I used recently included the recipe for the sauce, of course, and listed those steps after the whole chicken preparation part. That'd be fine, except the last line? "Cover and chill [sauce] for 2 to 4 hours." Would've been good to know two to four hours ago, thanks.
What are your recipe complaints?
