Odd not including French and Italian recipes.
it's a clickbait title
All of human cooking compressed into 2 megabytes
61–70 of 181 posts
Re: All of human cooking compressed into 2 megabytes
#62I don't see why the title needs to be quite so grandiose.
It's an appeal to the attention economy. "All of human cooking compressed into 2 MB" is(mentally) palatable relative to "Navigating the Emergent Geometry of Food Ingredient Embeddings". Getting you to click is the ultimate goal.
Should be downvoted/flagged and buried.
Re: All of human cooking compressed into 2 megabytes
#63WTF? I found this a parody. Perhaps because I've just been re-reading C.S. Lewis's "That Hideous Strength", where language becomes meaningless, I can't stand the design of the site or the text it presents.
Making a nice lentil soup doesn't require any thought or description. I know that I, and millions of cooks in Asia will do it with just their hands.
Re: All of human cooking compressed into 2 megabytes
#64Re: All of human cooking compressed into 2 megabytes
#65The work is very interesting. The title is misleading. A better title would be: "all of human ingredients compressed into 1,800 primitives" There is little to substantively nothing about the actual cooking: preparation methods, proportions, etc. But the idea that tomato goes well with beef the whole world over is very interesting and useful for creating flavors that will go together, perhaps surprisingly. It will be…
+1.
On a side note (and maybe off topic), I am thinking about food pairing which is based on the idea that two ingredients sharing volatile aroma compounds or certain molecular families may have a potential sensory compatibility (broccolis and strawberries for example). I'd love to test those ingredients and find some unknown food pairings. But .. time is what it is (for now).
Re: All of human cooking compressed into 2 megabytes
#66Neat. I'm trying to compress recipes into little schematics https://leontrolski.github.io/recipes.html
This will perhaps be overkill for what you're trying to achieve, but there is Object Process Methodology (OPM)[1] which may be inspiration for modelling recipes. It looks similar to the methodology you're using, and as an example, expects the following type of modelling:
"peeling carrot" (process) consumes "washed carrot" (object)
"peeling carrot" (process) yields "peeled carrot" (object)
"peeling carrot" (process) yields "carrot peel" (object)
"finely dicing carrot" (process) consumes "peeled carrot" (object)
"finely dicing carrot" (process) yields "finely diced carrot" (object)
"prepare mirepoix" (process) consumes "finely diced carrot" (object)
"prepare mirepoix" (process) consumes "finely diced celery" (object)
"prepare mirepoix" (process) consumes "finely diced onion" (object)
"prepare mirepoix" (process) consumes "butter" (object)
"prepare mirepoix" (process) yields "mirepoix" (object)
The advantage of OPM is alignment of graphical and textual representations.
The downside of such approach is you soon discover how many millions of objects may exist in recipes--unwashed carrot, washed carrot, orange carrot, purple carrot, yellow carrot, white carrot, peeled carrot, coarsely diced carrot, finely diced carrot, julienned carrot... and purple julienned carrot vs. yellow julienned carrot. And that's just basic preparation complexity well before any contemplation of cooking or plating up elements. To go further you then discover a lack of useful labels such as "mirepoix" or "soffrito", if for example, you wanted to substitute sweet potato in place of carrot in the recipe.
Then there is SysML 2[2] which is kind of like OPM if you ever wanted to write a recipe in 35,000 lines of code, including possibly all the complexity of mathematical modelling of the Maillard reaction for purple carrots vs. yellow carrots using either extra virgin olive oil or butter. Probably best suited for the largest food processing companies such as Nestle, Unilever, Modelez, etc and even then, inherent complexity of their food products rarely would reach the level of a fine dining dish prepared by a chef.
[1] https://en.wikipedia.org/wiki/Object_Process_Methodology
Re: All of human cooking compressed into 2 megabytes
#67Neat. I'm trying to compress recipes into little schematics https://leontrolski.github.io/recipes.html
Great initiative ! So simple and yet it works (from those recipes listed I know, they are all working nicely).
Re: All of human cooking compressed into 2 megabytes
#68Neat. I'm trying to compress recipes into little schematics https://leontrolski.github.io/recipes.html
Ahh - the dependency graph recipe card. These are excellent. I've imagined something like this forever. Always annoyed that recipes put ingredients in a giant undifferentiated list and then give an instruction like "mix the dry ingredients in a deep bowl". For a while I expected there could be a good return on a good implementation of this, but now as soon as a strong interface itself is created it seems easy to copy…
I used to want this kind of recipe card, but I've cooked so much that's no longer the case (I actually forgot all about the idea until reading this comment). I can usually look at the list of ingredients, and imagine what needs to be done. If it's an unusual or unfamiliar cuisine I will read the method, but after that point the list of ingredients suffice. If I read a recipe somewhere and want to cook it later, I will just write the ingredients on a post-it (usually in cooking order) and maybe 1-2 brief comments.
I imagine in domains you are skilled at you'd also prefer high level instructions than a step-by-step tutorial.
I agree that doesn't help the beginner, or someone who doesn't cook regularly, or someone cooking something new and I think most recipe writers are just following the established structure without thinking about what they and others really need.
Re: All of human cooking compressed into 2 megabytes
#69All of recorded human cooking compressed into 2 megabytes
We've lost more than we know
Re: All of human cooking compressed into 2 megabytes
#70Neat. I'm trying to compress recipes into little schematics https://leontrolski.github.io/recipes.html
I'd prefer it if you minimized the crossing paths :-)