|
|
|
|
|
by hinkley
1687 days ago
|
|
You need multiple rating systems for recipes and the lack of that model is why recipe sites are bullshit, and will continue to be bullshit. A recipe that tastes bad should never be shown to anyone. But if there are two flavorful recipes and one of them has better instructions, then that's the one that should be sorted to the top. My go-to analogy for people being bad at documentation is to compare them to the variation in quality in cooking recipes. That's both a commentary on developer docs and on chef's docs. I have been reworking a highly rated pie recipe. They have not covered browning the crust. They have made no mention of order and grouping of ingredients. If you follow the recipe literally, you're going to end up with a fluffy mix that won't fit in the pie tin. You're also going to get lumpy spices. That has a rustic appeal, but as the picture does not have lumps, the author is just bad at documentation. In my version, I split the spices so that you get a little texture but most are homogenized. I'm still experimenting with number of eggs. I've had 2 eggs (as in the recipe) taste eggy, and 3 eggs (minus a little egg white for the crust) taste fine, depending on how good the emulsion is, and that depends on order. Most recipes still seem to be built on a model of fear and social barter. Fear that if Aunt Susie figures out Grandma Beth's brownie recipe, then nobody will 'have' to invite Grandma Beth to holidays or at least be excited to see her. If you want brownies then you need Grandma Beth. |
|