Live data from Hacker News

Thinking about recipe formats more than anyone should

rknight.me

11–20 of 140 posts

Re: Thinking about recipe formats more than anyone should

#11
Here's an idea. A recipe is ultimately a checklist. It's essentially a multi-flow checklist with parts that need to be done sequentially and other parts that can be done in parallel.

So if we had a checklist format, we could easily derive a recipe format from that.

Re: Thinking about recipe formats more than anyone should

#12
With latest LLMs I feel there is less and less need to be structured about authoring recipes.

I now jot down rough notes in Obsidian when I make a meal I like, and let AI re-format it if I want to share the full recipe with somebody. This also lets me control the output: if I’m sending the recipe to somebody who is new to cooking, I might ask for a more detailed output than if they were only interested in my flavour combinations or specific techniques.

Re: Thinking about recipe formats more than anyone should

#13

Many years ago I experimented with making recipes into Gantt charts. For more complex recipes this proved incredibly useful. I spent some time trying to automate turning some of the recipe formats into Gantts, but it was pretty cumbersome. I'll bet a good LLM would make this achievable now. For an example, here's a gantt chart for Beef Bourguignon: https://ibb.co/c3TVTnX Note that when I print it on a (physical) reci…

Reminds me of the cookingforengineers.com format to some degree.

Here's an example. You'll need to scroll down to see the actual recipe format. https://www.cookingforengineers.com/recipe/194/Cream-of-Mush...

Re: Thinking about recipe formats more than anyone should

#15
Just finished my own overthinking of recipe structures. I figure that a recipe is more or less an upside-down tree!

Where you start with a list of all the nodes (ingredients)

Have a n:1 relationship with the next series of nodes (steps)

until you finish at a single node (the dish you're trying to make)

So instead of having a separate chunk of "here's my ingredients" and "let me repeat the ingredients and one by one instruction until the end" I figure you can display the upside-down tree to convey more information with less words.

An example being https://cookbook.cstebbins.com/recipe/bul-koki

With the underlying tree structure looking like https://assets.cstebbins.com/cookbook/images/bulkokiTree.png

Re: Thinking about recipe formats more than anyone should

#16
post #13

Many years ago I experimented with making recipes into Gantt charts. For more complex recipes this proved incredibly useful. I spent some time trying to automate turning some of the recipe formats into Gantts, but it was pretty cumbersome. I'll bet a good LLM would make this achievable now. For an example, here's a gantt chart for Beef Bourguignon: https://ibb.co/c3TVTnX Note that when I print it on a (physical) reci…

Reminds me of the cookingforengineers.com format to some degree. Here's an example. You'll need to scroll down to see the actual recipe format. https://www.cookingforengineers.com/recipe/194/Cream-of-Mush...

Hmm interesting. But I have to confess I have no idea, intuitively, how to read that format. I’m sure it works once you understand it, but if you need an instruction manual for the format then maybe you’ve lost the plot a bit.

Re: Thinking about recipe formats more than anyone should

#17
post #15

Just finished my own overthinking of recipe structures. I figure that a recipe is more or less an upside-down tree! Where you start with a list of all the nodes (ingredients) Have a n:1 relationship with the next series of nodes (steps) until you finish at a single node (the dish you're trying to make) So instead of having a separate chunk of "here's my ingredients" and "let me repeat the ingredients and one by one i…

Ha, your example makes intuitive sense right when you see it. Really clever thanks for sharing it!

Re: Thinking about recipe formats more than anyone should

#18

With latest LLMs I feel there is less and less need to be structured about authoring recipes. I now jot down rough notes in Obsidian when I make a meal I like, and let AI re-format it if I want to share the full recipe with somebody. This also lets me control the output: if I’m sending the recipe to somebody who is new to cooking, I might ask for a more detailed output than if they were only interested in my flavour…

Yeah, personally I'd use markdown too, at this point it is easier to use llama-3.1-8b to parse markdown / text into your JSON format of choice than it is to massage recipes into a specific markup like Cooklang.

Re: Thinking about recipe formats more than anyone should

#19
post #15

Just finished my own overthinking of recipe structures. I figure that a recipe is more or less an upside-down tree! Where you start with a list of all the nodes (ingredients) Have a n:1 relationship with the next series of nodes (steps) until you finish at a single node (the dish you're trying to make) So instead of having a separate chunk of "here's my ingredients" and "let me repeat the ingredients and one by one i…

ofc, trees

Re: Thinking about recipe formats more than anyone should

#20
IMHO for mostly text data where you need a bit of custom formatting(e.g. cooking recipes) I would probably choose to go with AsciiDoc and then just adapt a rendering engine to make it look pretty. This way you get all the tooling and learnings that AsciiDoc has accumulated over the years and avoid having to spend time on a DSL and edge case detection that inventing a new standard will require.
Post reply on HN