Cooking to impress and cooking to feed aren’t the same thing — and confusing the two is where a lot of food loses its meaning.
When I’m cooking to impress, I like to take people around the world. Different cuisines, mixed techniques, unexpected combinations. In a restaurant kitchen, everyone has a role, and the chef is working with the team to create something new, exciting, and full of flavor — sometimes something that even looks different than what people expect. Social media can feed that side of cooking. I use it to stay aware of what’s happening globally, to see new ideas, or to spark a direction I hadn’t considered before.
There’s nothing wrong with that kind of cooking. It pushes boundaries. It keeps things moving. It can be fun.
But cooking to feed is different.
Cooking to feed is how I cook at home. It’s simpler. Still done with proper technique. Still built on good ingredients. But I’m not switching cuisines every night or trying to surprise anyone. It might be spaghetti with meat sauce — something familiar — even though the restaurant version might be a Bolognese that takes hours and layers of refinement. At home, a lot of it comes down to time. I want to be in and out of the kitchen in 20–30 minutes during the week. Sundays are different — Sunday dinner gets more care. But during the week, it might be tacos, grilled meats, or seafood. Simple food, cooked well.
The trap comes when you try to do too much. When restraint and judgment disappear.
Here’s the contradiction most people miss: you can take a great piece of fish or a good steak, season it with nothing more than salt and pepper, grill or sauté it properly, finish the fish with a squeeze of lemon, the steak with a good compound butter — and you’re eating extremely well. There’s no hiding behind sauces or extra elements. You just have to know what to do with what you have — and know when to stop.
When you’re cooking to impress, the reaction you’re chasing is: “I would never have put those flavors together,” or “I’ve never seen that technique used like that.” That can enhance the experience, but it’s a fine line. Push too far and the dish stops making sense. Now you’re guessing for the sake of guessing.
When you’re cooking to feed, the bar is different — and higher in a way people don’t talk about. If you’re making pot roast, it better be as good as someone’s mom made it… or better. You’re pulling on memory. On comfort. On trust. You’re stepping into someone’s culture, and that comparison is unforgiving. If the dish doesn’t take them back, you’ve lost them.
That’s why cooking to feed is harder.
I try to stay aligned with the direction of the menu. I like having homey dishes alongside simpler preparations — food that doesn’t need explanation. Cooking done extremely well, without hiding behind excess. Fresh herbs instead of heavy sauces. Balance instead of overload. And here’s a small truth that says a lot: I’d rather eat a flat iron steak than a filet mignon. Flat iron has more flavor. Tenderloin may be soft, but it lacks depth. Flat iron is tender and honest.
Link: How I Decide When a Dish is Actually Good Enough
Link: Why I Cook With What I Have: The Skill That Made Me a Better Chef
Link: What I Do When the Recipe Doesn’t Make Sense: A Chef’s Approach
Cooking to feed demands humility. You’re not just cooking food — you’re handling someone’s memory. That’s why people joke, “Who made the potato salad?” Certain dishes belong to certain hands. Certain cooks. Certain stories.
Cooking to impress gets attention.
Cooking to feed earns trust.
Knowing the difference — and choosing correctly — is where judgment lives.
