Edit: I didn't realize this before writing the post, but what I'm referring to is The Principle of Charity.
Story
I was confused about Node Modules, so I did a bunch of research to figure out how they work. Explaining things helps me to understand them, and I figured that others might benefit from my explanation, so I wrote a blog post about them. However, I'm inexperienced and still unsure of exactly what's going on, so I started the blog post off with a disclaimer:
Disclaimer
I'm a bit of a noob. I just graduated from a coding bootcamp and am still trying to wrap my head around this stuff myself (that's actually why I'm writing this article). I tried to do my research, but I can't guarantee that everything is correct. Input from more knowledgeable people is very welcome.
My friend said that it's a bad idea to do that. He said:
You're literally discrediting yourself in the first sentence of the article. Stand by what you've written!
I interpreted what he said literally and basically responded by saying:
Why should I "stand by what I've written"? What I mean to communicate to the readers is that, "I'm x% sure of what I'm about to say." To "stand by what I've written" is to assign a higher confidence to the things I've written than what my true confidence is. It wouldn't even be a stretch to interpret "stand by what you've written" as meaning "claim that you're 100% sure of what you've written". Why would I do that?
This was stupid of me. He didn't mean "claim that you're 100% sure of what you've written". He didn't mean "pretend that you're way more confident in what you've written than what you really are". He meant, "I think that it comes across as you being less confident than you actually are. And so I think you should reword it to better communicate your confidence."
I shouldn't have interpreted what he said so literally. I should have thought about and responded to what I thought he meant to say. (Although, he also should have been more precise...)
Thesis
People often interpret and respond to statements literally. Instead of doing this, it's often useful to think about and respond to what the other person probably meant.
For example, "If I interpret what you said literally, then A. But you probably meant X, so B. If you meant Y, then C."
Depending on how confident you are in your interpretation, you should probably respond to a variety of possibilities. Like if you're < 80% sure that you know what they meant, you should probably respond to possibilities that have at least a 5% chance of being what they meant. I'm not sure whether 80 and 5 are the right numbers, but hopefully it communicates the point.
Why don't people do this?
I see two likely reasons:
- The whole "argument is a war that I must win" attitude.
- Habit.
For me, the problem with this is that if I'm speaking to an autistic person(and a very large number of LWers identify themselves as on the autistic spectrum), they tend to use literal meanings very often. In fact, some of them(including me) get offended or confused when they say something literal and it is interpreted as sarcastic or subtext.
Suppose I am speaking to an autistic person, and he says, "I am 87% confident that X is true." The issue with this statement is that a lot of people use this sort of statement in a metaphorical sense(ie. they just pull the number out of their butt to make it oddly specific and get a cheap laugh) but an autistic or rationality-trained person may literally mean that they are 87% sure it is true, especially if they are good at measuring their own confidence levels. In this case, the usual situation- the number being picked randomly - is false.
There are also, however, a large number of statements that are almost always meant sarcastically or in a non-literal way. The statement "I, for one, welcome our new alien overlords" is almost always sarcastic as it is 1) invoking a well-known meme which is intended to be used in this manner and 2) it is extremely unlikely that the person I am speaking to is actually someone who wants aliens to take over the world. These statements are, for want of a better word, "cached non-literal statements"(as in, it is an automatic thought that these statements are not literal), or CNLS for short.
It might be useful to append the guideline "All statements have a probability of being literal that is worth considering, except in the case of CNLSes. This probability is adjusted up if the person you are speaking to is known for being extremely literal and adjusted down if they are known for using figurative speech(although that last sentence should be fairly obvious, I throw it in for the sake of completeness)" to your thesis.
This actually got me thinking if there is a methodical, objective and accurate way to find out if someone's statement is literal or not, perhaps by measuring their posture, tone of voice. The only difficulty is to try to weasel some quantifiable data out of context. If it can be done, that would be a great resource to people who have trouble understanding the non-literal meanings of statements everywhere.
Give me all the bacon and eggs you have.
Wait, wait. I'm worried what you just heard was, "Give me a lot of bacon and eggs." What I said was, "Give me all the bacon and eggs you have". Do you understand?
-Ron Swanson