Picture this: you land somewhere new, drop your bag, and post in the group chat. “In Lisbon, where do I eat tonight?” Within an hour you have eight names. Three of them closed during the pandemic. Two are tourist favorites that locals stopped going to in 2018. One is great if you’re willing to cab forty minutes across town. One is “the one with the tiles, you can’t miss it.” And one is actually correct, but you’ll never know which.

That’s not advice. That’s social noise. People answer because the question made them feel included, not because they have a real read on your night. And then we treat the noise like data. We optimize against it. We schlep across the city. We end up tired, mid-meal, far from where we wanted to sleep.

The recommendation is only as good as the context behind it

Most restaurant suggestions get given like permanent truths — “THE place for ramen in Tokyo” — when the actual answer depends on what neighborhood you’re sleeping in, what hour it is, what mood you’re in, what you can spend, and what is actually open right now. Strip those out and the recommendation collapses into a brand name.

I notice this most when friends visit my city. Someone asks me “where should we eat?” and my honest answer is a question: where are you sleeping, what time, are you up for a thirty-minute walk, are we drinking, are we three or six, do you want to actually talk or are you fine yelling? If they roll their eyes I know they want a name, not an answer. So I give them a name. They’re usually underwhelmed. Of course they are. They asked the wrong question, and I gave them the wrong shape of reply.

Friends, dates, and group chats all fail in different ways

Friends default to whatever place was good for them, on the night they went, with the people they were with. The variables are baked in. Dates default to whatever feels socially safe — nice enough, not too weird, won’t embarrass anyone. Group chats default to whatever name has momentum that week. None of those defaults are about you, your hour, or your block.

The locals you actually want to ask — the ones who eat out four nights a week in your exact neighborhood — are usually not in your phone. They are at the counter you walked past. They are the cook’s cousin. They are a hairdresser two doors down. You can’t crowdsource them. You can sometimes read the room they’re sitting in.

What I actually ask now

When I have a friend who genuinely knows a city, I stopped asking them “where should I eat?” That question is too big. I ask smaller, more honest things instead.

  • What’s a place near where I’m sleeping — not on the other side of town?
  • What works at this hour? Lunch and 9pm are different cities.
  • What’s the version of this where I don’t need a reservation?
  • What place do you actually go back to, not just the one you took your visiting cousin to?
  • What place is good even if I’m alone with a laptop?

The answers to those are useful. The answer to “where should I eat in Mexico City” is not.

The honest part: I’m not the smartest source either

I’ll cop to it — even after building this thing, my own recommendations to friends are biased toward the four neighborhoods I happen to live near, the hours I happen to eat at, and the budget I happen to be on this year. That is fine for me. It is not fine as a source of truth for you. We all have a tiny radius of real knowledge. The honest move is to stop pretending the radius is bigger than it is.

The food answer should come from the live local situation, not from stale social memory.

What this changes about how I plan a night

I stopped pre-booking dinners more than a day out unless it’s a real occasion. I stopped trusting cross-city recommendations from people who haven’t been there in a year. I stopped asking the group chat. I anchor on where I am physically standing, what hour it is, and what is actually alive within a ten-minute walk. The hit rate went up, the regret went down, and the meals started feeling like part of the trip again instead of an errand.