Someone has cooked for you. You're four bites in, the food is good, and there's a small calculation running in the back of your head about when you're going to get your phone out.
You already know how this goes. Either you do it now and someone says something, or you tell yourself you'll remember and you won't, or you put the phone away for good and the meal just doesn't exist as far as your record is concerned.
None of the tracking advice I've ever read has anything to say about this. It's all scales and databases, as though the only thing between you and a logged dinner were information. Most of the time the thing between you and a logged dinner is four other people.
What the phone does to the table
The thirty seconds isn't the cost. The cost is that logging is visible, and visible tracking isn't a neutral act in company.
It invites a question — what are you doing, are you on a diet, is that one of those apps — and now the meal is about your eating, which is not what anyone sat down for. Worse, it can land as a comment on everybody else's plate. Someone who was enjoying their food now isn't. The person who cooked starts apologizing for the butter.
That's the real bill, and it gets paid by other people, which is why most of us quietly stop presenting it. We put the phone down, and the meal never gets written down.
And the meals that go unrecorded this way are precisely the ones worth having in the record. Meals with other people are bigger, richer, less predictable and less like the rest of the week than anything you eat standing up in your own kitchen. A log with every solo lunch in it and none of the dinners is a log of the part of your eating that was already easy to guess.
Almost nothing requires you to do it at the table
Here's the part that took me embarrassingly long to notice: the only reason to log a meal while you're eating it is that you're worried about forgetting.
That's a real worry, but it's a smaller one than it feels. An hour later you can still tell me it was chicken thighs and rice and there was definitely butter and you had two helpings. The thing you'd lose by waiting isn't the meal, it's a bit of resolution on the portion, and portion resolution was never the accurate part of any of this anyway.
So the table isn't where tracking happens. The car is. The walk home is. The ten minutes on the sofa afterwards. You can be the person who was actually at dinner, and be the person with a complete log, and the gap between those two things is about ninety minutes.
The line between later and too late
I want to be careful here, because I wrote almost the opposite thing a week ago — that you shouldn't rebuild a missed day out of memory, because memory fails by omission and the omissions all run the same direction.
Both are true, and the difference between them is the size of the gap.
One meal, the same evening, is memory doing what memory is good at. You were there an hour ago, you have a clear picture of the plate, and you're recalling a specific thing rather than reconstructing a general one. A whole day at two days' distance is memory at its very worst: you get the dinner you remember and you lose the four o'clock handful you never registered.
The rule I'd actually give you is that the record gets made while you can still see the plate in your head, and before you go to sleep.
That second half is not a flourish. An entry lands on the day you write it, so last night's dinner written down over this morning's coffee goes onto today — today reads high, yesterday reads short, and neither number says why. The car, the walk home, the sofa, the last thing before bed are all the same evening as far as your log is concerned. Breakfast tomorrow is already a different day.
Don't interrogate the cook
The other half of eating with people is the temptation to ask what's in it.
I'd resist that one hard. "Is there cream in this?" is not a neutral request for information at somebody's table — it's a question about their cooking, and they will hear it that way no matter how you phrase it. You are asking them to justify a dish they made for you.
An estimate costs you very little here and the question costs a lot. Say it was a creamy pasta, assume the cream, call it generous and move on. If you're logging a plate someone else made, you're estimating anyway — what you'd get from cross-examining the cook is a slightly better guess and a slightly worse evening.
And you don't owe the table an explanation for any of it. If somebody does ask, a plain answer is fine and usually ends it — I keep track of what I eat, it takes a second. The thing that draws attention isn't tracking. It's being visibly furtive about tracking.
What I built for this
Graham is a conversation, so logging a meal is one sentence in the past tense — roast chicken, potatoes, way too much of both — typed or said whenever you get to it. There's no search box to work through and nothing to scan, which is most of why it can wait until you're in the car: the job is small enough that being late doesn't make it bigger.
Estimates are welcome rather than tolerated, so a plate somebody else cooked doesn't need a conversation with them first. He'll say what he assumed and you can correct it in four words if he's wrong.
And his own reminder, if you turn it on, is built on the same idea. It comes in the evening, and it's past tense — what'd dinner end up being?, or one of a few lines like it. It arrives at most once a day, and only on a day you've already logged something, so it can't turn into a cold nag.
The part of it I'd actually defend is that you answer it where it lands. Type the reply into the notification and it's logged; the app never comes to the front and the phone goes back in your pocket. That is the car, exactly — a question about a meal that already happened, answered without the thing ever becoming an event.
The evening is the part that isn't negotiable
This doesn't make tracking invisible, and at some tables it's going to be awkward whatever you do. People notice things. Somebody who has decided your eating is their business will find the opening whether your phone is out or not.
What I can tell you is which half gives. If it ever comes down to a choice between a good meal with people you like and a clean record of it, the record is the one you can afford to lose. It'll still be roughly right if you write it down in the car, and if you don't write it down at all, you had dinner with your friends, which was the better of the two things on offer anyway.
— Ryan