Recipe Notes

Why the same recipe never quite turns out the same way twice

More chilli last time? Longer on the simmer? Without a record of what you actually did, the good version becomes a memory you're trying to recreate rather than a result you can reliably repeat.

You make a curry, and it's good — really good, better than usual. Six weeks later you make it again, following what you're fairly sure is the same recipe, and it's fine, just not quite that good. Something's different, and you can't put your finger on exactly what. More chilli last time? Longer on the simmer? A different brand of tin tomatoes? Without a record of what you actually did, the good version becomes a memory you're trying to recreate rather than a result you can reliably repeat.

The gap between a recipe and what you actually cooked

A written recipe is a starting instruction, not a record of what happened. The first time you make something, you're following the recipe. By the third or fourth time, you're following the recipe as filtered through your own adjustments — less salt because it ran too salty last time, an extra five minutes because your pan runs cooler, a swap because you were out of an ingredient and it turned out better anyway. None of that gets written down anywhere, which means every future attempt starts back at the original recipe, not at the improved version you actually landed on.

This is a strange kind of forgetting, because it's not that you don't remember making the dish — you remember it clearly. What's lost is the specific detail of how you got the good result, which is exactly the part that matters if you're trying to repeat it.

Every future attempt starts back at the original recipe, not at the improved version you actually landed on.

Why this matters more for some recipes than others

Simple recipes tend to survive this fine — there's not much to forget about how to roast a chicken. It matters more for anything with room for judgement calls: how long something actually needs on the heat in your specific kitchen, how much of a strong flavour is actually the right amount for your household's taste, what substitution worked when you didn't have the original ingredient on hand. These are exactly the details that make a recipe genuinely yours rather than just a copy of someone else's — and exactly the details most likely to be lost between attempts.

What actually helps

• A place to jot down what you actually changed, attached to the recipe itself, not a separate note somewhere that won't be there next time you're cooking
• Recording it close to when you cooked, while the adjustment is still fresh, rather than trying to reconstruct it weeks later from memory
• Being able to see it again the next time you pull the recipe up, so it's part of the recipe going forward, not a one-off thought that gets lost

Where mmmiso fits

Keeping recipes in one searchable place is the groundwork for this — the recipe you actually cook from is there every time, rather than scattered across a screenshot you might not find again. Attaching a running note of what's actually worked, adjustment by adjustment, is the kind of small feature that turns a saved recipe into something that improves each time it's used, rather than staying frozen at whatever the original source happened to say.