All of human cooking compressed into 2 megabytes
95 points by josefchen 6 hours ago | 34 comments
throwme_123 3 minutes ago
I would not trust a model/corpus about food that includes English and German, but excludes Italian and French
replyleontrolski 2 hours ago
Neat.
replyI'm trying to compress recipes into little schematics https://leontrolski.github.io/recipes.html
michelb 2 hours ago
Nice! this reminds me of https://www.reddit.com/r/flowchartrecipes/ and the table view on the https://www.cookingforengineers.com/recipe/87/Carrot-Pulp-Ca... pages.
replyteeray 2 hours ago
I like it. Reminds me a bit of the table format on Cooking for Engineers (scroll to the bottom of the recipe): https://www.cookingforengineers.com/recipe/19/Erics-Chocolat...
replyflobosg 56 minutes ago
I was going to say the same! You can also check the recipe card here: https://www.cookingforengineers.com/recipe/19/Erics-Chocolat...
replykarhuton 43 minutes ago
These are amazing. It feels so clear to see a visual ”map” of the cooking process before you even start.
replyThis would help coordinate two cooks to make prepping more independent.
I’m trying to figure out if an landscape Ipad, with interactive elements for extra details if needed, would be a good UI for this.
-
Edit: Showed it to my non-Engineer wife and she said ”this is horrible” after staring at it for 10 seconds. Maybe not for everyone…
ultimatefan1 26 minutes ago
My friend did a similar thing
https://www.kickstarter.com/projects/1077776268/recipe-redes...
replyNiloCK 2 hours ago
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".
replyFor 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.
nyokki 4 minutes ago
As someone learning to cook from recipes in multiple languages,
this is really cool. Curious how it handles the same ingredient
called by different names (e.g., "scallion" vs "green onion" vs
"long onion").
replyRetr0id 54 minutes ago
> [Claude] performed all ingredient classification under deterministic decoding (temperature 0–0.1)
replyNot that it matters much in this context, but low-temperature is not the same thing as deterministic.
haaz 2 hours ago
Published by Kaikaku, a London based startup doing automated restaurants and cooking
replyskinfaxi 16 minutes ago
Cooking/recipes seems like it would be an excellent application for a specialized model.
replysuddenlybananas 2 hours ago
I don't see why the title needs to be quite so grandiose.
replymuragekibicho 60 minutes ago
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".
replyGetting you to click is the ultimate goal.
1970-01-01 28 minutes ago
11 sources is not "all of" anything. You have a sample. The title is horrible. Fix the title please.
reply
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 a nice resource in the future.
https://www.nature.com/articles/srep00196
I saved a beef stew I was making for twelve people once by adding tomato sauce.
Beef hardens if stewed incorrectly and tomato acid tenderises it again.
EDIT: removed incorrect information about store bought tomatoes.