Or if any of the steps requires a more complicated instruction that can’t be expressed in a few words. It wouldn’t break the structure of the diagram, but it wouldn’t be as beautiful.
It is a fun idea though, maybe there is another format that works.
Similarly, it also easily identifies which part of the recipe each ingredient goes to. You can do this by splitting up the ingredients list as well, but that doesn’t really go against it being a good idea.
I find this layout works best for in-the-moment reference while cooking, and the 2-dimensional nature of it is what really makes it useful. So I think of splitting an ingredient as like lifting some of it out into an imaginary third dimension before inserting it later at another step.
I believe this design breaks down once you prepare an ingredient that then gets split for use in two or more later steps.
But now I’m thinking which kind of diagram could be used as well. Some adaption of an UML activity diagram maybe?
Or if any of the steps requires a more complicated instruction that can’t be expressed in a few words. It wouldn’t break the structure of the diagram, but it wouldn’t be as beautiful.
It is a fun idea though, maybe there is another format that works.
This diagram is classic “engineer developing a solution for a problem that doesn’t exist in a domain they don’t understand”
The diagram does have benefits. For example it shows which steps can be performed in parallel if multiple people are cooking.
I don’t need a diagram to do that but maybe my experience is atypical
Similarly, it also easily identifies which part of the recipe each ingredient goes to. You can do this by splitting up the ingredients list as well, but that doesn’t really go against it being a good idea.
I’m a software “engineer” and also passionate about cooking. Both are arts. You can’t reduce it to an algorithm
And concise! No more frantic scrolling on my phone with batter-covered fingers
I ran into this exact issue when I was making these diagrams for my own recipes: https://git.tilde.town/gamerdonkey/recipes_for_engineers#known-issues . My workaround was just to have instructions to set some aside and use it later.
I find this layout works best for in-the-moment reference while cooking, and the 2-dimensional nature of it is what really makes it useful. So I think of splitting an ingredient as like lifting some of it out into an imaginary third dimension before inserting it later at another step.
List it twice?
No.
Can’t an ingredient be there twice?
But you want to do the first phase together
Then two tables? Or rows in the middle to mark the action to split the ingredient in 2?
rows in the middle to mark the action to split sounds the best to me
Create a separate card for that ingredient, and in the main card list “add X% of <other card>”
I like that idea, if only for the fact that it opens the door to recursive recipes.
A pie with itself?