Microblog Memes

What if you wanted to first sift, combine and whisk the dry ingredients before folding in, would you put that in the big blank square box?

I’ve also invented similar recipe design on note cards, mainly because I fucking hate having to find quantities of things I didn’t premeasure.

Fuck mise en place I want to see quantities as o add them.

anything can be Marie Kondo'ed, it would seem.

I don't know, what's a recipe without a popup video and six banners and a "jump to recipe" button that doesn't work, as well as 99 pictures of spaghetti?

Here's an open source library for generating these from markdown https://mossblaser.github.io/recipe_grid/tutorial.html

But where am I going to put the six paragraph AI generated anecdote about my grandmother?

The hallmark of recipe design imo was modernist cuisine and the following books on pizza and bread. A lot of the recipes were obnoxious and it’s written by a notorious ex Microsoft cto that turned into a patent troll to finance his cooking nerd bullshit (morally justifiable to pirate all of the obnoxiously expensive books) but props for their recipe format

Very clear, in order of addition, scaling percentages, and in the actual book clear instructions follow which is extremely helpful in the bread one especially

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.

While they were at it, they could've solved the problem with "pre-".

"There are only two states an oven can possibly exist in: heated or unheated!" - Carlin

COOKING FOR ENGINEERS!!!

I learned how to cook from this site like 20 years ago! I still use that format on my home recipe cards sometimes, but now I've just gotten so used to it all recipes look like this on my head. Great format, taters guna tate.

The real site also includes a paragraph description, this is just a quick reference card that's assuming you have already cooked the recipe a few times, not great for learning it the first time.

What does that mean? What does fold in mean?

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 ...

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/

Kind of reminds me of the output of qdirstat.

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.

I first saw this notation technique on a recipe card pinned to a stove from the 1850s at a preserved historical village display. I have no reason to doubt that it was the original card, or descended from it.

I believe this design breaks down once you have a step that prepares 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?

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)").