6 ms·
For me, the context and reasoning behind why the recipe does what it does is much more important than the recipe itself; that makes such apps counterproductive.
by soamv 5y ago
For me, the context and reasoning behind why the recipe does what it does is much more important than the recipe itself; that makes such apps counterproductive.
I can imagine that "just the recipe" is useful for very novice cooks, but most of the time it's much better to learn the patterns and techniques than to follow the precise recipe. You'll be much more prepared that way when things don't go to plan, or when you're missing a few ingredients.
And this may be unpopular here, but I often enjoy the "life story" too: for me, many of the joys of cooking are in the connections made to other people. And if the recipe writer wants to build a connection with the cook because they poured so much effort into the recipe, I'm open to that -- and whatever it may bring to the actual cooking.
(Maybe I should make a "just the code" browser extension for Github that deletes README files ;) )
- jagged-chisel 5y agoThe common complaint is about the unnecessary prose around the author's life history and other fluff that's useless to the goal of producing the food item. IME, seldom do those sites actually contain useful information about cooking practices in addition to the fluff.
- soamv 5y agoIt's not fluff to me -- it's human connection. Why we cook the way we do is deeply linked to our history and our "life stories".
- datavirtue 5y agoIt's not human connection. It is SEO fluff. Made up garbage.
- butwhywhyoh 5y agoIf README files were: 1. Full of tangential life-story BS 2. Placed far above the content I went to the repo for 3. Filled with advertisements I would love your browser extension. Also, you claim the story is "much more important" than the recipe itself. So then I guess you would enjoy these recipes pretty much equally if they completely removed the ingredients of what they actually cooked? It's so much less important, after all.