Increase names their APIs using the “vocabulary of the underlying network.”

Wyatt’s about to leave for a trip.

I say he can call whenever, don’t worry about the time difference.

He says, I know I should call. And squirms.

I say, I didn’t say you should call, I said only that you could. It was an offer, not an imperative, not an obligation. Please don’t feel obligated.

We talk it through. I say he “should” just go have a great time, and call only if he wants or needs to.

A little later:

Wyatt.

What.

Were you also uncomfortable, because by mentioning the call-anytime-offer it brought into relief the fact that you’re going on your first big trip away, and you didn’t want more attention on it because you’re also doing a lot of processing yourself, inside?

Yes, I think that’s going into it.

Cool.

I won’t call this API the “uncomfortable conversation” or “miscommunication” API. Maybe I’ll call it the “newness discomfort” API, and its integration looks like seeing and naming the deeper sea the person is swimming in, then acknowleding their efforts. WIP.