Skip to content

Why your best dish shouldn't have a recipe

  • mindset
  • technique

You cook from recipes, and you cook them well. Phone propped against the canister, you measure what it says to measure, add things in the order it lists, set the timer for the minutes it gives you. It comes out the way it’s supposed to. Everyone eats. And some quiet part of you notices that it felt less like cooking than like assembling something from a manual — careful, a little anxious, not really yours.

You have a friend who doesn’t cook like this. They open the fridge, and forty minutes later there’s dinner, and when you ask how they made it they can’t quite say — “I don’t know, the usual, a bit of this.” You file that under talent: the kind you weren’t born with.

You were. The difference between you and that friend isn’t a gift. It’s that they’ve made their dishes enough times, and changed them enough times, that the recipe fell away. Your version is the real recipe — and you get to yours the same way they got to theirs.

Skip this and you stay a faithful follower forever. The food’s always good — and always someone else’s. You keep reaching for your phone to make the dish you’ve made more times than you can count.

There’s no original to be faithful to

The recipe in front of you is already somebody’s version. Someone made the dish, nudged it toward their own taste, and wrote down where they happened to land. The “authentic” one underneath it isn’t there — go looking for the one true guacamole and you’ll turn up a hundred cooks who each leave something out and swear the others are ruining it.

So following a recipe to the letter isn’t more correct. It’s making the writer’s version instead of your own. You have exactly as much right to a version as they did. The only difference is they wrote theirs down.

How a dish becomes yours

One change at a time, and the changes are small.

Take a basic tomato sauce for pasta. The first time, you follow it — onion, garlic, a tin of tomatoes, the pinch of sugar it tells you to add, simmer. Fine. But you thought it could take more garlic, so next time you double it. The time after, you drop in a dried chili, because you like some heat and nobody’s stopping you. Then you notice your tomatoes are sweet on their own and you quietly leave out the sugar. One night you stir a knob of butter in at the end. It goes glossy and round, and that’s never coming back out.

Six months on, you’re not making the recipe anymore. You’re making the thing it became in your kitchen — and if you set the original back in front of you now, you’d find it thin. You didn’t invent a sauce. You changed a few things and kept the ones that were better. That’s the whole skill.

The changes are the proof you understood it

You can only change a dish well if you know what each part is doing. Leave out the sugar because you understand it was there to balance the acid, and your tomatoes already handle that — that’s a different act from leaving it out because you forgot. One is a cook making a call. The other is a guess that got lucky.

So the changes aren’t a flourish on top of competence. They are the competence. The moment you change something on purpose and it works, you’ve proven you understood the dish well enough to move it — the exact thing the recipe-following version of you couldn’t do.

Changing a dish keeps it from going stale, too — but that’s a different argument. Here the point isn’t variety. It’s that the changes are yours, and so is the dish.

Keep the ones that work

What turns a lucky night into a dish you own: write the change down. Not filed away somewhere — on the recipe itself, in the margin, in your own hand. More garlic. No sugar. Butter at the end. Next time you don’t start from zero; you start from your last best version and change one more thing.

Do that across a dozen dishes and you’ve built something no download can hand you: a cookbook of food that tastes like you. Not recipes you collected — recipes you wrote, by cooking them until they were yours.


A while from now, someone at your table asks you to send them the recipe for the thing you just made. You go to find the link, and there isn’t one — not really. There’s something you started from two years ago and a dozen changes you’ve made since that live nowhere but your hands. So you write it out for them: the garlic, the chili, the butter, the no-sugar. Your version. The real one.

Not a hard dish, not a fancy one — just one you’ve made enough times, and changed enough times, that it came out the other side as yours.

Your version is the real recipe. You don’t get there by collecting more of other people’s — you get there by understanding one dish well enough to change it, and then changing it until it’s yours.