Your Best Recipes Aren't Written Down
You never cook a recipe the same way twice. The best version of any dish lives in your head — and that's the problem.
Our bolognese started as someone else’s recipe. It called for red wine, celery, and a long simmer. We skip the celery now. We use white wine instead of red because that’s what we usually have open. We add a spoonful of miso at the end — something we tried once on a whim and never stopped doing.
The original recipe is saved in a bookmarks folder somewhere. It’s not wrong, exactly. It’s just not ours anymore.
This happens with every dish you cook more than a few times. You adjust. You learn what your family actually eats. You discover that your kids will eat it if you dice the onion finer, or that it’s better with smoked paprika instead of sweet. The recipe drifts, and the version in your head becomes the real one.
The problem with writing it down
The obvious answer is to keep notes, and maybe you do for a while. A scribble in the margin of a cookbook or a comment in a Notes app that you’ll never find again. But recipe notes are messy. They’re not “swap ingredient A for B”, they’re “use less liquid if the tomatoes are really ripe” or “start the rice earlier because the stove runs hot.”
That kind of knowledge doesn’t fit neatly into an ingredients list. It’s contextual. It’s personal. And it builds up over dozens of cooking sessions, not one.
I mean who even bothers. We cook, we learn something, and then forget it by next Tuesday.
Every recipe is a conversation
The word “recipe” implies something fixed; a set of instructions you follow to produce a result. But that’s only true the first time. After that, cooking is a conversation between you and the dish. What worked? What would you do differently next time?
Home cooks carry this history in their heads. They know that this chili needs an extra fifteen minutes despite what the recipe says, to double the garlic because the written amount is timid, or that the trick is to let it rest even though the recipe doesn’t mention it at all.
That knowledge is worth something, but where do we put it?
Why this matters
We’re not talking about professional chefs with kitchen notebooks. We’re talking about the Tuesday night cook; the person trying to get dinner on the table while managing everything else. For them, losing a small improvement means repeating the same mistakes, or never quite reaching the version of the dish they know is possible.
Recipes should evolve. They should remember what you learned and get better every time you cook them.
That’s what we’re building with Dillr. When you debrief after cooking, your notes and tweaks get folded back into the recipe. Next time you open it, you’re already at a better starting point.
