A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
RULES:
RELATED COMMUNITIES:
I made an app where the the recipe is saved as a JSON file with ingredients separate from the steps. In the steps instead of saying "mix sugar and butter" if says "mix {sugar} and {butter}" and the app adds quantity there directly. I can scale the recipe and still have the quantities inside the body ("mix sugar (100g) and butter (55g)").
Nice! I thought about doing the same and then discovered https://cooklang.org/ - looks like it's a similar approach that you describe
I tried recreating this style of recipe card and ended up using a JSON tree structure to store the recipe. I also added fields for a little more description so that I could generate a little more traditional lists for ingredients and instructions.
https://git.tilde.town/gamerdonkey/recipes_for_engineers/
Example recipe: https://tilde.town/~gamerdonkey/recipes/lemony_olive_oil_zucchini_bread.html JSON representation: https://tilde.town/~gamerdonkey/recipes/lemony_olive_oil_zucchini_bread.json
What if the recipe steps include modifiers like ‘add half of the butter’?
It will simply say "Add half o the butter (100g)" and you have divide it yourself. It's very simple.
BUT
Some recipes will have the same ingredient multiple times like:
Filling:
- 100 g sugar
- 50 g butter
Dough:
- 500 g flour
- 100 g butter
and the app will distinguish between them and put the correct amount in the correct part of the body.
This seems like it wouldn't scale well for more complex recipes, and for the given example I'd prefer a list of steps instead, e.g.
I think it depends on how much of a verbal versus visual thinker you are. I'm very much the latter, and I've been using the Cooking for Engineers template for years. One nice thing about it is still having an ingredient list for shopping or mise en place and steps together without repeating a bunch of text.
Also, bigger recipes will usually have parts that are done concurrently, and the boxes with those steps will stack vertically. The example is one sequence all involving the butter, so that's already really the worst case scenario for this format.
Those are good points! Thanks for sharing.
People already complained about every other aspect but my favorite is "completely authentic 100% original guarantee just like the origin city" and you open up the ingredients list to see half the stuff using localized substitutes.
If I wanted to make a homemade half assed version of the thing, I would have done it myself. I'm here to see how it's actually made dammit.
Jalapenos are not substitutes for thai chillies just because they're both peppers.
My dyslexic brain hates this. Words and lists are better.
My typical brain hates this too.
My (probably) autistic brain loves it.
It's a neat diagram, but I'm unsure what they mean by "ignore it." This is exactly how good recipes have been designed for many many decades, minus the nifty visual cheat sheet and with better instructions. [i.e. Do you beat the eggs? How thoroughly? How do you know when it's done baking?]
I absolutely get that this might help those who are more visually based learners, but the structure of recipes already follows this pattern. This turns the written instructions into a simplified chart, and I hope more thorough written instructions are simply being elided here.
I do like it though. It would certainly make a nice visual shorthand to glance over at during prep.
I think the diagram is especially useful for those who have done a recipe numerous times.
This seems like a great visual summary and useful for those who can refer to it and use experience to fill in the details.
Nothing substitutes a raw cooking instruction in plain language.
What am I even making here?
espresso brownies, apparently
Thank you for blindly trying out the recipe to see what it makes for us.
It's actually kind of crap. The first two lines are things you do, then suddenly it shifts to lines being ingredients and columns being things you do. As someone else pointed out, it's not completely obvious which ingredients go into the mixing step one after the other. Also, if you have a recipe where you have steps to make ingredients used later on, it kind of falls apart.
I would not want to use this to make lasagna!
I use an adjusted version of this format, and yes, one of my adjustments was putting all steps including initial setup together on the right.
Also, for many ingredients introduced together in one step, I simply order those ingredients top-to-bottom in whatever order it's ideal to add them in. I can't think of any recipes where that alone wasn't enough, but if I did need to provide more info, that would either be done in the text or justify splitting that step into multiple steps.