i wish all recipes were presented this way. every single one of them.
GetBetter
anything science based to improve, health, mental, technics, skills
Nah sorry doesn’t appeal to me at all.
Yea, this format sucks.
Yeah, this is actually beautiful!
But what is the recipe for? There's no title.
I get it, some kinda cookie right? But still
Autism didn't exist 50 years ago! Autism 50 years ago:
This isn't a recipe? Recipes have 40 paragraph long stories about how your grandmother fell in love in Rome .
You Americans just can't get away from the corporate brainwashing no matter how hard you try.
"Hershey's cocoa powder", what the fuck? Not only is naming a specific brand for a recipe bad enough, naming the worst shit imaginable is so fucking weird.
Sometimea it is important like when a recipe wants American jiff or skippy peanut butter etc, because it contains icing sugar besides just peanuts; which changes sugar ratios for cookies.
My guess is that it has to do with the variations from brand to brand and clarifying that this particular recipe used that brand to get the expected taste. Assuming they didn't enshitify their version with cheaper ingredients.
Though I hate recipes that say something like "one can" or "one package". Even without shrinkflation, different brands sometimes use different sizes (if no brand is specified).
Though if it's a published recipe, I agree with the other comment saying that money probably exchanged hands, and that deal might even be the only reason that recipe is featured at all, because it was probably a "publish recipes that sell more of our shit" rather than "fit our shit into your recipes where possible". Guessing the whole thing might have started with "inventory of our cocoa powder is piling up, sales team gets a bonus if they can get it sold (and we'll lay off the people producing it for a bit)".
pity us.
We deserve no pity
Perhaps the recipe calls for vomit flavored chocolate that other brands cant match.
Nah, it's the delectible combination of wax and vegetable oil.
Typically that just means there was some kind of endorsement deal with the company that made the recipes. I doubt this is an exclusively American phenomenon.
I love this. And to all the guys arguing whether this is a good way of designing a recipe, please remember you are on Lemmy, most people here are either it or engineers or at least very close to one of those professions so the amount of autism is significantly increased 😂
I'm not sure an excel chart is that much better than just saying "melt x, mix y, fold z and then bake" and the list of ingredients xyz.
Yeah, what if you want to do something like "seperate the yolks from the whites, beat the whites until they're fluffy and then add sugar and mix with the rest." And then a later step doing something with the yolks. I don't see how you would do that here without it turning into an unreadable mess.
I like it as the shorthand at the end. Special instructions could still be included before it as usual.
It works for very simple recipes where the work can be summed up in a word or two. Complex recipes need far more instructional information not just the order to put ingredients together.
This chart works well as both the requirements and process reference.
The fine details can be asterisk line items afterward.
Then the family story goes at the bottom, with perforations so you can tear it off and toss it out
Then the family story goes at the bottom, with perforations so you can tear it off and toss it out
Stop you gorgeous creature, I don't want to fall in love with you, I don't even know you.
I once came across a cooking blog that used this sort of instructions over a decade ago; was apparently run by an engineer - haven’t found it again since, but the methodology stuck with me.
I believe www.cookingforengineers.com , but it’s either down or doesn’t like my VPN, so I can’t verify.
Definitely not a VPN issue; I’m raw dogging the internet on my phone and also getting a Server 500 error.
Will bookmark to try and remember to revisit it at some point in the future. 😅
Here's an open source library for generating these from markdown https://mossblaser.github.io/recipe_grid/tutorial.html
Exactly what I was hoping existed already. I think I'm going to try and convert some recipes to this format and see how it goes. I like that it has the ingredients in a simple list, makes shopping so much easier.
I don't understand what this adds that the "traditional" recipe style is missing. I even see some things it's lacking. For example, the last 4 ingredients should be mixed together independently before folding in to the base.
I don't dislike this format, but I just don't see why it's so revolutionary.
It clearly shows the sequential and parallel threads of execution:
- up/down: parallel.
- left to right: sequential
It clearly shows the sequence of produced intermediate results, split and merging points:
- a row that splits into two rows is one step producing more than one result. Like spliting yolk and whites.
- many rows becoming one: merging node. Like baking many ingredients.
If the last 4 ingredients need mixing together first, then you simply have a mix column with just those ingredient rows under the mix column from above to show that those get mixed independently in parallel. This recipe implies that is unnecessary for this food though.
My wife said "But how will we learn their life story!?"
This is pretty much useless unless the recipe is strictly additive. No room for "split a chunk of dough, we'll need it later". Or if you need to prepare two things in parallel before combining some but not all. Or indicating that a step can progress unattended.
https://mossblaser.github.io/recipe_grid/tutorial.html#splitting-recipe-components-up
someone figured out a way