Why not say something like “hey, I’m bowing out of this conversation now, but it’s not intended to be any sort of reflection on you or the topic, I’m not making a statement, I’m just doing what’s good for me and that’s all”?
That seems fine too, if I feel like putting the effort into writing a long thing like that, customizing it for the particular circumstances, etc. But I’ve noticed many times that it’s a surprisingly large effort to hit exactly the right balance of social signals in a case like this, given what an important and commonplace move it is. (And I think I’m better than most people at wordsmithing this kind of thing, so if it’s hard for me then I worry even more about a bunch of other people.)
Even just taking the time to include all the caveats and explanations can send the wrong signal—can make a conversation feel more tense, defensive, adversarial, or hypercautious, since why else would you be putting so much work into clarifying stuff rather than just giving a chill ‘bye now :)’?.
Avoiding that takes skill too. I think this is just a legit hard social thing to communicate. Having another tool in my toolbox that lets me totally ignore one of the most common difficult things to communicate seems great to me. :)
(And indeed, with your second paragraph I see that you’re spotting some of the issues. We can just pre-despair of there being any possible solution to this, but also maybe the jargon would just work. We haven’t tried, and jargon does sometimes just work.)
“I suspect I would start to attach that same meaning to any code phrase” and “I think that even talking about either using a code phrase or to spell it out inevitably pushes toward that being a norm” are both concerns of mine, but I think I’m more optimistic than you that they just won’t be big issues by default, and that we can deliberately avoid them if they start creeping in. I’m also perfectly happy in principle to euphemism-treadmill stuff and keep rolling out new terms, as long as the swap is happening (say) once every 15 years and not once every 2 years.
That seems fine too, if I feel like putting the effort into writing a long thing like that, customizing it for the particular circumstances, etc. But I’ve noticed many times that it’s a surprisingly large effort to hit exactly the right balance of social signals in a case like this, given what an important and commonplace move it is. (And I think I’m better than most people at wordsmithing this kind of thing, so if it’s hard for me then I worry even more about a bunch of other people.)
Even just taking the time to include all the caveats and explanations can send the wrong signal—can make a conversation feel more tense, defensive, adversarial, or hypercautious, since why else would you be putting so much work into clarifying stuff rather than just giving a chill ‘bye now :)’?.
Avoiding that takes skill too. I think this is just a legit hard social thing to communicate. Having another tool in my toolbox that lets me totally ignore one of the most common difficult things to communicate seems great to me. :)
(And indeed, with your second paragraph I see that you’re spotting some of the issues. We can just pre-despair of there being any possible solution to this, but also maybe the jargon would just work. We haven’t tried, and jargon does sometimes just work.)
“I suspect I would start to attach that same meaning to any code phrase” and “I think that even talking about either using a code phrase or to spell it out inevitably pushes toward that being a norm” are both concerns of mine, but I think I’m more optimistic than you that they just won’t be big issues by default, and that we can deliberately avoid them if they start creeping in. I’m also perfectly happy in principle to euphemism-treadmill stuff and keep rolling out new terms, as long as the swap is happening (say) once every 15 years and not once every 2 years.