A few years ago I had one of those meals. A small place in Trieste — I'd wandered in off the street, ordered something I couldn't quite pronounce, and ended up staying for two hours. The food was extraordinary. The room had that particular quality of somewhere that's been doing the same thing well for a very long time.
Six months later, a friend was planning a trip to Trieste and asked me for a recommendation. I had nothing. Not the name, not the street, not even the neighbourhood. I remembered the feeling with total clarity. I couldn't tell him a single fact about the place.
This is a specific kind of frustration — losing something that mattered not because the memory was bad, but because you never gave it anywhere to live.
Why restaurants are so easy to lose
Place is one of the strongest anchors human memory has. The ancient Greeks knew this — the method of loci, a memorisation technique over two millennia old, works precisely by attaching information to imagined locations. The spatial brain is good at holding things.
But "place as anchor" only works if you revisit the place, or revisit a record of it. A restaurant you went to once, in a city you don't live in, gets no retrieval practice. The memory isn't reinforced. It fades.
And restaurants are particularly prone to this because we experience them in a state that's actively hostile to encoding: we're relaxed, often a glass of wine in, absorbed in conversation. The pleasure of the meal is exactly what makes it hard to remember later. We're not paying attention to the details in a way that would make them stick.
The result: a long mental list of "that place we went to that time" that gradually becomes "somewhere in Lisbon, I think" and then nothing at all.
When to capture it
The right moment is the same evening, before you leave or shortly after.
Not the next day. By the next morning you've already lost the specific details — the name of the dish, the thing the waiter mentioned about where the wine came from, exactly why the atmosphere worked. These are the things that make an entry useful later. They evaporate quickly.
The note doesn't need to be long. Sixty seconds is enough. The goal is to catch the facts while they're still warm.
What to actually record
A restaurant entry is useful when it contains:
The name and location. Sounds obvious, but the name is the first thing to go. Write it down while the sign is still visible. If you can attach a GPS location, do — maps don't lie about where you were.
What you ate. Specifically. Not "pasta" but "cacio e pepe." Not "some kind of fish" but the actual name if you can remember it. The specific dish is what makes an entry vivid when you read it back.
Who you were with and why you were there. Context is what makes a memory meaningful rather than just informative. "Dinner with L. after the exhibition" tells a story. "Restaurant in Trieste" is just a log.
A rating. Even a simple one to five. This is the thing that makes the data actually useful — because six months later you won't remember whether you left satisfied or disappointed, and without a rating you can't filter. The rating is the one number that lets you answer "where should we eat?" rather than just "where have I been?"
One line of text. Not a review, not a summary. Just the thing that made this place different from every other restaurant. "The best focaccia I've had in years." "Loud and chaotic but somehow exactly right." "Go back and try the fish." One line is enough.
Building a personal map of places
The individual entry is useful. But the value compounds when you have enough of them to navigate by.
Imagine opening a map and seeing every restaurant you've ever logged — pinned by location, filterable by rating or occasion. You're heading to a city you visited two years ago. Instead of trying to remember what was good there, you just open the map and look. The five-star pins tell you where to go back.
This is the difference between a food diary and a personal atlas. A diary is a record of the past. An atlas is a tool for the future.
For this to work, you need consistency more than volume. Logging ten restaurants a year, reliably and with a rating, is more useful than logging fifty with no system. The filtering requires clean data. A half-remembered entry with no rating is noise.
Finding favourites again
The other thing a good restaurant log gives you: the ability to answer "where should we go?" with something other than "I don't know, anywhere."
We're bad at this question under pressure. We can't pull names from memory reliably. We forget that the great neighbourhood place exists because we haven't thought about it in four months.
A searchable list of your logged restaurants, sorted by rating, solves this. Especially if you've noted the occasion or mood — "casual, weeknight, just the two of us" — because you can match to the current situation rather than just the highest-rated option overall.
I've found this genuinely useful for repeat visits. Before a trip to a city I know, I check what I logged last time and whether I wrote "must go back." That note, made after the meal when the feeling was fresh, has sent me back to places I would have forgotten to revisit. Usually they're as good as I remembered.
My own experience
I started logging restaurants seriously a few years ago, originally just as a list in a notes app. Name, city, rating, one line. It took thirty seconds per entry and I was consistent about it.
Two things happened that I didn't predict.
The first: I stopped having the Trieste problem. Places stopped disappearing. When someone asks for a recommendation in a city I've visited, I have an answer that's actually specific.
The second: reviewing old entries became unexpectedly pleasurable. Reading back through two years of restaurants isn't just useful — it's a record of the meals and people and circumstances of those years. The dinner before a job interview. The place we went for a birthday. The solo lunch in a city where I didn't know anyone. The food is the frame. Everything else is the picture.
This is the thing that keeps the habit going when the practical utility alone might not. The entries accumulate into something more than a list of places. They become a kind of geography of how you've spent your time.
The app question
Any system you'll actually use consistently is the right one. A spreadsheet, a notes app, a physical notebook — the format is secondary to the habit of capturing before you forget.
That said, combining a rating system with map-based logging makes the data significantly more useful, because you can navigate by location rather than scrolling a list. I built an app called Remember that does exactly this — map view, categories, ratings, one tap to log. It's described on the Places hub if you're curious.
The Trieste place is still out there. I didn't log it in time. That's a small regret, and an easy one to stop repeating.