My dyslexic brain hates this. Words and lists are better.
My typical brain hates this too.
My (probably) autistic brain loves it.
You should probably mix together the dry ingredients before folding them in. So the big blank square in the bottom middle should be “mix” but I guess that ruins the cascading aesthetic and makes it more cluttered, which would’ve also showed the weakness of this design
Also why would you fold in the dry ingredients, maybe this is just some “lorem ipsum” recipe but unless there’s a foam you’re trying to keep inflated you don’t really need to fold stuff in.
So the big blank square in the bottom middle should be “mix”
is see that as an improvement. that square was empty and unbalanced space before
showed the weakness of this design
i guess when you generate such a design per script, then you can replace some of the straight lines with flowing/wavy lines and get a nice design again. (i am thinking like a sankey diagram maybe? but there are probably other more compact variants possible)
Why is mix included twice?
Mix the sugar, vanilla, and coffee first. Then mix in the eggs.
it’s two different steps, but I don’t find the chart so intuitive,
IMO there shouldn’t be borders between the actions and ingredientsedit: that would make it worseOh. I think then the table would benefit from an additional row up top of subheading columns featuring step numbers (1, 2, 3, etc) to make that clearer.
Annoying that they did not even mention the original site: https://www.cookingforengineers.com/
Which does seem down right now, so archive link: https://web.archive.org/web/20260729050049/https://www.cookingforengineers.com/
Interestingly, not the whole site is down, but the homepage is
Damn, even that site has a life story before a recipe
Very cool tho
If you put a recipe on your webpage Google will ignore that shit. Butter and eggs? So few words, many numbers. Boring.
So you have to add a narrative if you want search engines to pay any attention, or even count the page as content.
Google could just fix this, but no, we’ve all adjusted to it.
I had no idea it was about too few words. I always thought it was that they add all that fluff to maximize their advertising revenue, making you scroll and scroll through a story before you find the recipe. Seems like either way, it’s thanks to Google….
Maybe originally a couple decades ago, but every food blog template added a “jump to recipe” button pretty shortly after those started to be a thing.
I found the recipe but apparently the design in the OP wasn’t perfect, they have slightly updated it: https://www.cookingforengineers.com/recipe/327/Espresso-Brownies
This guy was the foundation of my cooking skills… 20 years ago. Damn.
The site being down fits with the ‘for engineers’ theme
Just because we can’t code for shit and insist on doing everything ourselves…
Joking aside, it was down because it got Reddit hugged to death, since a post on the frontpage of /r/all mentioned it in the top comment.
Now it’s back online
Absolutely love this way of setting it up! but it’s only almost perfect. It has weight in mass instead of volume and temperature converted to celsius. I only need a proper measure of the pan and it would let me make it without any conversions.
This is kind of a normalized process diagram to illustrate functional programming paradigms. I read this as it was posted in a programming community here on Lemmy a couple of months ago:
https://www.lihaoyi.com/post/WhatsFunctionalProgrammingAllAbout.html
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.
Now I want chocolate cake or whatever this is making.
Brownies. I’d go with this recipe over the one in the OP, though.
Ah yes, can’t go wrong with basically anything from Sally’s. Thank you!
Where’s the box for the story about how mother used to make this years ago and how the author made it for a such and such party and guests were asking for the recipe and …
I want to read the authors complete backstory and several holiday pictures and sales pitches on why I should buy their artisanal ingredients, scrolling until I nearly give up.
I feel like the recipe loses authenticity since there is no backstory about how their great uncle came up with the recipe after falling out of a guard tower during WWII.
deleted by creator
I actually vibe coded a script that would jump your browser to the recipe for that exact purpose.
That sounds cool and all, but can you vibe code a script that injects more heart tugging stories and additional AI images before I get to the recipe? It should feel like Im wading through slop to find what I’m looking for.
justtherecipe.com is pretty great for cutting out that crap, although not as efficient as the system in OP pic
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 saw cooklang but only after I made my app. It’s interesting but for me the main goal was to use existing recipes. I wanted to just take something I found online and be able to use it, not have to rewrite it. And I wanted it to handle multiple languages. When the first decent LLMs came up I did some testing and they were capable of transforming recipes into JSON so I build my app around that but the JSON had to very simple. I later managed to add couple extra features (like groups of ingredients) but it’s still way simpler than cooklang. Current LLMs could handle cooklang without issues but my app already does everything I need it to do so I’m not changing anything.
Ah very interesting! I found cooklang to be overkill for my needs as well but the fact that there’s an obsidian plugin resulted in me using it now.
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 butterand the app will distinguish between them and put the correct amount in the correct part of the body.
Sauce or is it proprietary?
https://f-droid.org/en/packages/net.curiana.recipes/
Desktop (Linux only) version is here: https://github.com/kandrelczyk/twili-recipes/releases/tag/0.2.10
Disclosure for AI vegans: The app integrates with external LMMs to parse recipes into JSON but they can also be added manually.
sugar and butter do tend to go into sauces
Plus then when I want to swap out eggs for I don’t know mustard or something it’s so much easier.
I do my recipe cards like this
Instructions unclear, went all in before folding, now I’m baked
Same, but not about the baking just the baked part.
Hucking fell. Ima just download it to remember this exists. Thank you
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.
Works for some recipes, but not all.
Also, more detailed instructions are needed. Mix for how long, till what consistency? Baking times and temps usually also say something like “… or until just brown”, or “…until crispy with dark edges.” Because, unlike machines with switches that do exactly the same thing each time, cooking has many variables that simple instructions don’t account for.
Add an asterisk or number to reference a footnote for the steps that need more instruction. This would work really well for a lot of recipes.
It’s best for recipes where you know the techniques already. These are reminders and not detailed tutorials.
Like my bread “recipe”, which I don’t even bother writing down anymore, is just: 1% gluten flour, 29% spelt, 70% AP, 85% water, 15% starter. Sit 90 minutes. 3% salt, 20-25% other. Stretch and fold every half hour until crackly. Split in two loaves, rise, bake at 500F w/steam tray 25 minutes, turn off oven 20 minutes.
There’s a lot of unwritten stuff there, but it fits on a card.
Yeah that’s a problem I’ve encountered with old recipes. Written by those who know the procedure they just need to write down the exact portions. My family’s got foods lost to time that we know the ingredients of but not the method.
Mix until creamed, mix until stiff peaks form, etc. Any of the “action” steps that require further instruction are going to really mess up this tidy format.





















