Sunday I made a thing I'd made before, a white bean, leek and escarole gratin. Previously? It was this delicious hearty cheesy comfort food. Sunday? Sad greens topped with cheese flavored sawdust. Part of the reason, I think, was the recipe called for ingredients by type - 1 leek, 1 head escarole, and the proportions got screwed up.
Something I find interesting with recipes are the ones that take you through the failures to get to the success- if version 1.0 had too many peas, v2 was too spicy, no one talks about v3, etc. It not only takes you through the process (admittedly, "food" and "too much detail" are pretty much my hobbies), but can also help understand the end result better. Understanding *why* there's only 1 cup of peas and not 1.5 is usually entertaining, and also gives me a base to put my own spin on whatever you did.
Also, I appreciate anything that shows the process so the messaging isn't "made this for hubs and YUMMO", it shows that food recipe development is both work and, at times, absolutely infuriating.
I agree with you, I usually find the more granular detail of recipe development fascinating. I try to keep it to a relative minimum while posting recipes because I want to keep the posts brief and easy to read. We all know the stereotype about food bloggers sticking 3000 word tomes before the recipe itself, and I try my best to avoid that. But maybe I’ll start giving a little more detail when it’s appropriate and adds to the recipe as a whole.
Sunday I made a thing I'd made before, a white bean, leek and escarole gratin. Previously? It was this delicious hearty cheesy comfort food. Sunday? Sad greens topped with cheese flavored sawdust. Part of the reason, I think, was the recipe called for ingredients by type - 1 leek, 1 head escarole, and the proportions got screwed up.
Drives me insane when this happens. Like come on, I didn’t really change that much, I don’t deserve to have this much of a divergent result.
EXACTLY. That was so good, this? This is prison food. I made nutriloaf.
Something I find interesting with recipes are the ones that take you through the failures to get to the success- if version 1.0 had too many peas, v2 was too spicy, no one talks about v3, etc. It not only takes you through the process (admittedly, "food" and "too much detail" are pretty much my hobbies), but can also help understand the end result better. Understanding *why* there's only 1 cup of peas and not 1.5 is usually entertaining, and also gives me a base to put my own spin on whatever you did.
Also, I appreciate anything that shows the process so the messaging isn't "made this for hubs and YUMMO", it shows that food recipe development is both work and, at times, absolutely infuriating.
More YUMMO, got it.
I agree with you, I usually find the more granular detail of recipe development fascinating. I try to keep it to a relative minimum while posting recipes because I want to keep the posts brief and easy to read. We all know the stereotype about food bloggers sticking 3000 word tomes before the recipe itself, and I try my best to avoid that. But maybe I’ll start giving a little more detail when it’s appropriate and adds to the recipe as a whole.
Process, on anything, is endlessly fascinating to me.