chuckl

3 ms·

1. 1.▲
   by chuckl 2y ago

   100% 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
2. 2.▲
   by chuckl 2y 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
3. 3.▲
   by chuckl 2y 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 secti
4. 4.▲
   by chuckl 2y 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.
5. 5.▲
   by chuckl 2y ago

   thanks for checking it out!
6. 6.▲
   by chuckl 2y 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) u