chuckl
Joined 12 years ago
Karma
39
Submissions
6
Member since
Nov 11
Recent submissions
Comment · 1 year ago
Comment · 1 year ago
that's interesting! Same concept.
I initially got the idea from the book Cooking for Geeks https://www.cookingforgeeks.com/
I wonder if they got it from Cooking for Engineers
Comment · 1 year ago
for sure! The use case I'm solving for myself is easy lookup while I'm cooking which is different than the use case of me going shopping
Maybe someday I'll add a feature to grab a shopping list. Could organise it into sections of the store and do a quick traveling salesman problem :D
also due to the conciseness of the grid, it's also not great if you're making it for the first time
Comment · 1 year ago
I think of them as 2 different nodes, 2 instances of the same type of ingredient.
Practically I just have it listed twice if it's important like butter.
https://cookbook.cstebbins.com/recipe/the-best-swedish-meatb...
otherwise if it's a staple like salt I just say something like "stir in and season with additional salt and pepper to taste"
like in https://cookbook.cstebbins.com/recipe/sloppy-sophisto-joes
Comment · 1 year ago
thanks for checking it out!
Comment · 1 year ago
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
under the hood I have it more like a graph with levels. The traversal is from all of the "leaves" to a single node rather than from the head node towards the leaves as in a traditional tree. The upside-down tree is more for a visual for the reader.
At the moment I don't have a recipe that outputs 2 end states but entirely possible since it's more of a graph under the hood.