Fennli Blog

Why "what can I make with this?" is the wrong question

Thu, 18 Jun 2026 00:00:00 GMT

You open the fridge at six-thirty and take stock. Half an onion, going soft. The last of Sunday's roast chicken. A can of corn you bought for something you've since forgotten. A bag of spinach a day from giving up. There's clearly food here. There's just no dinner.

So you do the modern thing and type it into your phone. What can I make with chicken and corn? The internet, eager to help, returns four hundred recipes — a chowder built on cream and a potato, a casserole that needs three things you don't have, a "quick" skillet dinner with a fourteen-item list. You scroll, you don't have the stuff, you close the fridge, and you order from the Thai place again.

You've decided the problem is one of two things: either you should have planned the week better, or you haven't found the right tool yet — the app with the ingredient filter that finally matches your fridge to a recipe. It's neither. The food is right there; planning was never the gap. And no filter will save you, because the problem is the question. "What can I make with these ingredients?" is a lookup — and a lookup hands you a stranger every time. Leftovers aren't a lookup problem. They're a question of whether you understand a few dishes well enough to feed them whatever's lying around.

The lookup always hands you a stranger

Say it works and you find the chowder. You've never made it, so you follow it the way you follow any recipe you don't understand — carefully, anxiously, hoping. Maybe it turns out well — but it solved exactly one fridge, once. Next Tuesday, with a different half-onion and a different sad vegetable, you're back at the search bar starting from zero.

That's the ceiling on the tool: it can match ingredients to a recipe, but it can't turn that into something you know, and it can't teach you anything that carries to next week. A hundred ingredient lookups leave you exactly as stuck as the first.

A dish you understand will eat almost anything

A cook does the opposite. They don't ask the fridge what recipe it matches. They look at the chicken, the onion, the corn, the limp spinach — and two or three things they already know how to make put their hands up.

Because they know what a fried rice is for: a hot pan, cold rice, whatever protein needs using, a handful of veg, an egg, something salty at the end. The chicken and the corn and the dying spinach aren't a puzzle now — they're exactly what fried rice eats. Or it's a frittata, which takes the same odds and ends bound with egg. Or a brothy soup, made from the chicken and anything green. The leftovers didn't change. The cook just knew where they could go.

That's the whole move. You're not matching ingredients to a recipe. You're feeding ingredients to a dish you already own.

Understanding is what makes the pantry stop mattering

This is why the skill beats the filter. The tool needs you to list what you have and go ask the internet, every night, forever. The skill means you open the fridge, see four sad ingredients, and the dishes that want them are already waiting. You stop "not having what the recipe needs," because you're not starting from someone else's recipe — you're starting from what's in front of you and steering it into something you know.

And the ask is small: five dishes you really know — a fried rice, a frittata, a soup, a grain bowl, a good pasta — already cover most of what a fridge throws at you.

Next week. Six-thirty, the fridge, the usual scraps — an end of cabbage this time, two eggs, rice from last night. You don't reach for your phone. You already know: it's fried rice, or it's a frittata, whichever you feel like. Dinner decided itself out of what was already there. Nothing got looked up. Nothing got thrown out.

Leftovers aren't a lookup problem. Understand a few dishes well enough, and there's almost nothing in your fridge you can't place.

Why you keep saving recipes you never cook — and why a tidier folder won't help

Thu, 18 Jun 2026 00:00:00 GMT

It's late. You're scrolling, and someone makes a thirty-second pasta that looks better than anything you've eaten this week. Your thumb finds the save button before you've finished watching. There — it's yours now. You'll make it.

You won't. It goes into the folder with the other three hundred: the sheet-pan dinners, the braises, the soup you screenshotted in February. You've cooked maybe four of them. But the three-hundredth save felt exactly as good as the first, and that's the part worth looking at.

It's not that you're disorganized. It's that saving feels like cooking, and it isn't. You can't save your way to knowing how to cook. The folder grows every week; the cooking stays where it was last year.

The collection gets bigger and more beautiful, and less likely you'll touch it. You start to feel like someone who's into cooking — you've got the evidence — while the cooking is the same five things on rotation. The gap between the cook you're collecting toward and the cook you are widens with every save.

Saving is the feeling of progress without the progress

The save is a tiny down payment on a better version of you. Tap, and for a second you're the person who makes the hand-rolled pasta thing on a Tuesday. The recipe is filed. You've handled it.

But you didn't cook anything. You bought the idea of cooking it, and the idea is free and the cooking is work, so the ideas pile up and the work doesn't get done. This is procrastination dressed as progress. It looks like motion toward something. You're just moving recipes.

A tidier graveyard is still a graveyard

The natural next thought is that the problem is the mess. Three hundred screenshots, no order, no tags — of course you never cook them; you can't even find them. So you go looking for the app that saves from anywhere, sorts by cuisine, strips the life story off the top. Clean. Organized. Searchable.

And now you have a beautifully organized collection of recipes you still won't cook. The tidying was a higher-effort version of the saving — the same hit of progress, the same zero dinners. The problem was never that the saves were messy. It's that saving was never the thing.

The pile does have one cost beyond the clutter — the more you've saved, the more there is to wade through every time. But that's decision fatigue: a different problem with a different fix, and more recipes won't fix that one either. Organizing your saves can shrink the pile. It can't turn a recipe you've saved into one you've cooked.

A recipe you've never made is a stranger

You learn it by cooking it — once, even badly. A saved recipe teaches you nothing. It's a set of instructions you don't understand yet, written by someone who isn't in your kitchen. You don't know which step decides whether it's good, or what sauté until softened looks like in your pan. Swap in the ingredient you don't have, and you can't tell if it'll survive. It's a stranger, and saving a stranger's number doesn't make them a friend.

Cooking it once changes that, and nothing else does. You make it, the garlic catches because you turned away for ten seconds, and now you know that's the moment to watch. You find out the sauce wants the acid at the end, not the start. That knowledge isn't in the recipe. It's in the one time you made it — and it carries, quietly, to the next dish that works the same way.

That's the real difference between someone who cooks well and someone with three hundred saves. It isn't the size of the folder. It's that the good cook has actually been through theirs — a short list of dishes made enough times to know cold. Knowing comes from the doing. There's no other door.

It's late again. The same kind of video — someone making something that looks better than your week. This time you don't save it. You pick the night you'll make it, and on that night you make it, and it comes out a little wrong in a way that tells you something. It's not in a folder. It's in your hands now. One dish you didn't have last week.

You can't save your way to knowing how to cook. You can only cook your way there, one dish at a time, until the folder stops being where recipes go to be forgotten.

Why your best dish shouldn't have a recipe

Thu, 18 Jun 2026 00:00:00 GMT

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.

Why you're bored of your own cooking — and why more recipes won't fix it

Wed, 17 Jun 2026 00:00:00 GMT

You're at the stove making the chicken-and-rice thing again. You could do it with your eyes closed — same pan, same order, same fifteen minutes. It'll be fine. Everyone will eat it. And somewhere around the point where the rice goes in, you notice you're a little bored. Not of cooking. Of cooking this, the way you always cook it, for what feels like the fortieth time.

So you do the obvious thing. You go looking for new recipes. You save a few. Maybe you cook one. Then the week gets busy and you're back at the stove with the chicken-and-rice, because it's the one you don't have to think about.

The problem was never that you cook the same few dishes. That's not a rut — it's how home cooking has always worked. The problem is you only know one version of each.

A dish you understand never gets old, because you can change it. The five meals aren't the cage. Cooking them the same way every time is.

Most nights aren't a project

The everyday meal is meant to be modest and repeatable — a handful of dishes you can make without thinking, in heavy rotation, for years. Not a performance. Not a new project every night. The whole point is that you don't reinvent dinner from scratch when you're tired — nobody can sustain that, and the people who try burn out and order in.

What keeps a meal like that from going stale isn't novelty. It's that you understand the few things well enough that small changes come for free. When the vegetable at the market changes, the dish moves with it. Same shape, different dinner. The repetition isn't the enemy. Frozen repetition is — the same dish made the identical way.

Where the dials are

Most dishes you cook on repeat are built on three or four moving parts, and you're probably only turning one of them — the protein. Leave that alone and look at the rest.

Take the chicken-and-rice. The bones of it are: brown the chicken, build a sauce in the pan it browned in, finish the plate so it tastes alive. Three moves. Now turn the dials.

Brown the thighs hard, then deglaze the pan with soy, a thumb of ginger, a spoon of honey; finish with sliced scallion. Now it leans Cantonese. Same thighs next week: soften an onion slow in the same fat, stir in smoked paprika and a tin of tomatoes, let it braise ten minutes, finish with chopped parsley. Now it's closer to a Spanish stew.

The chicken didn't change. The rice didn't change. You changed the aromatic, the cooking liquid, and the thing you finished with — three dials — and got two dinners that don't taste related. You didn't learn two recipes. You learned where the dials are on a dish you already make.

That's the difference between a rhythm and a rut. A rut is the same five meals, each with one setting. A rhythm is the same five meals, each with a dozen.

Why another recipe isn't the answer

This is also why the fix for boredom is almost never a new recipe. A new recipe is another thing to manage — a set of instructions to follow exactly because you don't understand it yet. That's how people end up with two hundred saved recipes and the same dinner every Tuesday — the saving feels like progress, and the cooking stays exactly where it was.

A dish you understand subtracts a decision. A recipe you saved adds one. Understanding is what lets you keep the collection small on purpose and still never eat the same week twice.

None of this means you never cook something new. Some weekends you want the project — the long braise, the bread you keep meaning to try, the thing you've watched three videos about. That's part of the joy, and you should do it. But you can't make a project of dinner every night; that's the exhaustion that drove you back to the safe five in the first place. The project is the exception. The rhythm carries the rest.

Next week. You're at the stove with the chicken again. But you brown it harder this time, and when the fond catches you spoon in that chili crisp from the back of the fridge, and you finish with lime instead of nothing. Same chicken. Same rice. A dinner you haven't had before. You didn't decide anything — you just knew which dial to turn.

A dish you understand never gets old. You don't need more recipes. You need to know the few you have well enough to change them.

Why your vegetarian soup is just fine and you can't figure out why

Tue, 16 Jun 2026 00:00:00 GMT

Sunday night. You made the soup — lentils, the holy trinity sautéed, stock, salt, pepper, in that order. It's fine. You eat it. You go back for seconds, partly because seconds is dinner, partly because you're trying to find what's wrong. You taste your way around the spice rack, add another pinch of salt, squeeze in lemon. The third bowl is better than the first, which tells you the answer is in the bowl somewhere — you're just not finding it.

This is the vegetarian soup tax. You took the meat out, and with it went a layer of flavor you didn't realize was load-bearing. Every soup recipe still quietly assumes the meat is doing background work. Yours can't. So the soup is fine, and you can't figure out why fine is the ceiling.

The missing something isn't an ingredient. It's a technique. Most "missing somethings" are skipped basics.

The base

Skimping on fat is where most vegetarian soups go quiet. You don't see it happen because the recipe still says "olive oil" and you used olive oil. But "two tablespoons in a big pot" is what a recipe says when the author hasn't decided whether you have meat fat to fall back on later. You don't. The oil is the medium that carries flavor in your soup; it's not greasing the pan.

Real amount: a glug that looks slightly too much, plus another half. Heat it until it shimmers — properly, not hopefully. Then the onion, carrot, celery. Salt the veg lightly here; salting now pulls water out of the vegetables and into the fat, which is what you want. Cook them until they're soft and a little sweet. Twenty minutes is normal. Not five. You'll know it when the onion has gone from translucent to faintly amber at the edges and the whole pan smells like something you'd want to eat on its own.

Garlic last in this base. Garlic burns at the temperature where onion is still happy, and burnt garlic turns the whole pot bitter.

The middle

Spices go in here, and this is where most recipes lie to you.

Cumin, paprika, thyme — pick three you like, but don't put them in the stock. Spice aromatics are mostly fat-soluble; they bloom into oil. Drop dried spices into a simmering pot and they sit there. Water doesn't pull the aromatics out — fat does. Add them to the base instead, after the veg is ready, before the liquid goes in. Toast for thirty seconds in the fat — the moment they're done is not subtle, you'll smell it.

Then the stock. Then the lentils. Salt the stock; this is your second salt layer. Red lentils break down in about twenty-five minutes; brown or green need longer. Don't simmer past tender — overcooked lentils take on a chalky note that nothing rescues.

The finish

Acid at the end is the single move that does the most work in the bowl, and it's the one most home cooks skip.

A squeeze of lemon. A splash of red wine vinegar. A spoonful of yogurt swirled in off-heat. Heat dulls your perception of acid, which is why a soup that tastes balanced on the stove can fall flat in the bowl ten minutes later. Acid lifts everything else — salt registers more clearly, the spices come forward, the lentils stop tasting heavy. Without it, you get exactly the experience you started with: fine, missing something, can't name it.

Salt one last time after the acid, not before. Acid sharpens your ability to taste salt; salting first leads to over-salting. That's your third and final salt layer.

Base, middle, finish. The missing something was never a secret ingredient — not fish sauce, not parmesan rind, not miso. Those are upgrades. They fix nothing if the three moves aren't there.

Next Sunday. You make the soup again. The base takes its twenty minutes and you don't rush it. The spices bloom in the fat before the stock goes in. The lemon goes in at the end. You taste it once and you don't reach for the spice rack — every flavor has its place.

Same lentils. Same trinity. Same stock. No meat. Better soup, because the technique caught up. Most "missing somethings" are skipped basics. That applies to lentil soup, and it applies to most of what you cook from here on.