But I was right, dammit! It's not a fallacy to use abbreviations if you're using them correctly.

Showing 3 of 5 replies (Click to show all)

The "fallacy" alleged here is not the using of acronyms, but your calling it a mind projection fallacy when I said a statement was deliberately obscure.

I was projecting a motivation onto the speaker. That's bad, but not actually the mind projection fallacy, because it wasn't my motivation that I was projecting. That was some other error; maybe the "Bad effects are caused by bad people" fallacy. The mind projection part would be me saying, "This statement is not clear to me; therefore, this statement is not clear."

Is that th... (read more)

0JGWeissman11yNo it is not a fallacy to use abbreviations correctly. I don't think anyone said it was. It can be a failure of communication to use even correct abbreviations the audience is not familiar with. And invoking the Mind Projection Fallacy, implicitly pointing out that the ignorance is in the mind of the reader who doesn't get it, misses the point that the communication failure lies in the failure to account for the probable ignorance of some portion of the audience, and communicate the point anyways by using full English words, which is rightly assigned to the commenter that used the abbreviation. Of course, I understand that you did not get all that from the phrase "deliberately obscure", which itself is the sort of vague accusation I think we should avoid. (And I also doubt the obscurity was deliberate.)
1thomblake11yCorrect - I wonder in what sense this is supposed to be a 'fallacy'. If anything, it more resembles skipping steps in a proof. Top-level comment to follow. ETA: link [http://lesswrong.com/lw/g3/catchy_fallacy_name_fallacy_and_supporting/d2c]

Catchy Fallacy Name Fallacy (and Supporting Disagreement)

by JGWeissman 1 min read21st May 200957 comments


Related: The Pascal's Wager Fallacy Fallacy, The Fallacy Fallacy

Inspired by:

We need a catchy name for the fallacy of being over-eager to accuse people of fallacies that you have catchy names for.


When you read an argument you don't like, but don't know how to attack on its merits, there is a trick you can turn to. Just say it commits1 some fallacy, preferably one with a clever name. Others will side with you, not wanting to associate themselves with a fallacy. Don't bother to explain how the fallacy applies, just provide a link to an article about it, and let stand the implication that people should be able to figure it out from the link. It's not like anyone would want to expose their ignorance by asking for an actual explanation.

What a horrible state of affairs I have described in the last paragraph. It seems, if we follow that advice, that every fallacy we even know the name of makes us stupider. So, I present a fallacy name that I hope will exactly counterbalance the effects I described. If you are worried that you might defend an argument that has been accused of committing some fallacy, you should be equally worried that you might support an accusation that commits the Catchy Fallacy Name Fallacy. Well, now that you have that problem either way, you might as well try to figure if the argument did indeed commit the fallacy, by examining the actual details of the fallacy and whether they actually describe the argument.

But, what is the essence of this Catchy Fallacy Name Fallacy? The problem is not the accusation of committing a fallacy itself, but that the accusation is vague. The essence is "Don't bother to explain". The way to avoid this problem is to entangle your counterargument, whether it makes a fallacy accusation or not, with the argument you intend to refute. Your counterargument should distinguish good arguments from bad arguments, in that it specifies criteria that systematically apply to a class of bad arguments but not to good arguments. And those criteria should be matched up with details of the allegedly bad argument.

The wrong way:

It seems that you've committed the Confirmation Bias.

The right way:

The Confirmation Bias is when you find only confirming evidence because you only look for confirming evidence. You looked only for confirming evidence by asking people for stories of their success with Technique X.

Notice how the right way would seem very out of place when applied against an argument it does not fit. This is what I mean when I say the counterargument should distinguish the allegedly bad argument from good arguments.

And, if someone commits the Catchy Fallacy Name Fallacy in trying to refute your arguments, or even someone else's, call them on it. But don't just link here, you wouldn't want to commit the Catchy Fallacy Name Fallacy Fallacy. Ask them how their counterargument distinguishes the allegedly bad argument from arguments that don't have the problem.


1 Of course, when I say that an argument commits a fallacy, I really mean that the person who made that argument, in doing so, committed the fallacy.