Here is the scariest thing you can do in a kitchen: open the fridge, look at what's there, and start cooking without googling anything first.
No recipe. No measurements. No step-by-step instructions from a food blogger who needs to tell you about their childhood in Provence before revealing that the secret ingredient is salt. Just you, whatever is in front of you, and the radical proposition that you might already know enough to feed yourself.
The first time I cooked without a recipe, I made something that can only be described as "technically edible." Overcooked onions, under-seasoned rice, a sauce that was ambitious in theory and confusing in practice. I ate it anyway. The world did not end. My kitchen did not revoke my access privileges.
The second time was marginally better. The fifth time was actually good.
Here's what nobody tells you about recipes: they're training wheels. They're incredibly useful when you're learning — how long to cook an onion, what temperature for roasting, why acid brightens a dish. But at some point, if you've cooked enough, the knowledge lives in your hands. You know what a properly softened onion looks like. You know by smell when garlic is thirty seconds from burning. You know that the dish needs "something" and that something is probably acid or salt or both.
You already know more than you think. You've absorbed it through repetition, the same way you absorbed language — not by studying grammar tables but by being immersed in it until the patterns became instinct.
The practice is simple: start with what you have. Open the fridge. What's there? An onion, some greens, half a lemon, eggs, cheese, that jar of something you bought optimistically three months ago. Good. That's dinner.
Step one: heat a pan. Add fat — oil, butter, whatever you have. This is the foundation of almost everything you'll ever cook. Hot pan, fat, patience.
Step two: start with the thing that takes longest to cook. Usually the onion. Cook it until it smells good. "Until it smells good" is a more reliable instruction than any timer, because your nose knows things your clock doesn't.
Step three: add things in order of how long they need. Dense vegetables before leafy ones. Dried spices before fresh herbs. Protein before garnish. The logic is always the same: hard things need more heat and time, delicate things need less.
Step four — and this is the one that transforms intuitive cooking from stressful to joyful — taste as you go. Constantly. Every few minutes. A tiny spoonful. Does it need salt? More acid? A bit of sweetness? Your tongue is giving you real-time feedback that no recipe can replicate, because a recipe doesn't know your specific onion, your specific pan, your specific heat.
Step five: when it tastes good to you, it's done. There is no other authority here. No blogger needs to approve. No photo needs to match. You made food. It tastes like something you want to eat. That's success.
The joy of cooking without a recipe is the joy of improvisation. It's jazz, not classical. You're responding to what's happening in the pan rather than executing a predetermined plan. Some nights the improvisation produces something brilliant. Some nights it produces something adequate. Both are fine. Both fed you. Both taught you something about what works and what doesn't.
Fail small. If you're not sure about a flavor combination, try it on a spoonful before committing the whole dish. If something isn't working, add acid or salt before panicking. If it's genuinely terrible, you've lost twenty minutes and some vegetables. That's a very cheap tuition for culinary education.
Tonight, close the recipe app. Open the fridge. Look at what's actually there. Start cooking.
You already know more than you think.
Trust your hands. Trust your nose. Trust the pan.