Journal / Behind The Scenes
Behind The Scenes - February 14, 2026
Why We Test Every Recipe Twice
By Mariana Estevez
A recipe is half ingredients, half assumptions. The first test, by the developer, confirms the ingredients. The second test, by a cook who has never made this dish, surfaces the assumptions. Did the developer know to keep the pan covered for the last five minutes because it makes the eggs softer? The instructions need to say so.
About a third of our recipes change between the first and second tests, almost always because something was assumed by the developer and missed by the home cook. Sometimes it is a word -- "thick" means three different things in three different kitchens, so we change it to a measurement. Sometimes it is a step -- "let it cool" gets a time, "season to taste" gets a starting amount.
This is slower than writing once and shipping. It is also what makes our library work in your kitchen. Every recipe in the system was cooked at least twice before it ever appeared on the site. It is the part of our work that nobody sees, but it is the part that matters most.
More from the journal
Why Cuisine Rules Exist (And When To Break Them)
Every great cuisine has a small set of non-negotiables. Knowing which ones really matter is the difference between a recipe that honors a tradition and one that fights it.
The Quiet Difference Between Stock And Broth
They both come out of a pot of bones and water, but stock and broth want different things. Knowing which one a recipe needs is half the battle.
Salt, Pepper, Acid, Fat -- And One More Thing
Samin Nosrats famous four have entered the language of cooking. There is a fifth element that most home cooks miss: context. A dish reads differently depending on what you ate before it.