conchis comments on Catchy Fallacy Name Fallacy (and Supporting Disagreement) - Less Wrong

23 Post author: JGWeissman 21 May 2009 06:01AM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (56)

You are viewing a single comment's thread.

Comment author: conchis 21 May 2009 09:19:03AM 9 points [-]

I agree that this is a danger, and that it's something we should be wary of, in both ourselves and others.

But I'm not sure we should require people to spell things out in excruciating detail every time they think someone else has committed an error. It's probably a good mental discipline to go through this process in your own head, to check that you're not firing off an unwarranted accusation, but sometimes it really is pretty obvious that a particular error has been committed, and in such cases the shorthand seems both useful and justified. If it's still unclear to others, I'm fairly sure someone will come forward and say so (and they should be encouraged to do so).

Maybe I'm wrong about this. I'd be interested in others' opinions.

Comment author: JGWeissman 21 May 2009 04:53:43PM 12 points [-]

It's probably a good mental discipline to go through this process in your own head, to check that you're not firing off an unwarranted accusation, but sometimes it really is pretty obvious that a particular error has been committed, and in such cases the shorthand seems both useful and justified.

It is really easy to give yourself too much slack when checking these things in your own head. Actually committing your justification to a public comment that others can scrutinize helps to honestly evaluate your own position.

Further, though it can be reasonable to present a position without support when no disagreement is expected, in the case of a counterargument, there is already disagreement, which you should attempt to resolve by presenting your actual reasons for holding your position.

If it's still unclear to others, I'm fairly sure someone will come forward and say so (and they should be encouraged to do so).

A large part of my motivation for this post was to encourage this behavior.

Comment author: Cyan 21 May 2009 03:08:17PM *  6 points [-]

...sometimes it really is pretty obvious that a particular error has been committed...

I favor more detail over less. Obviousness isn't an intrinsic characteristic of an error -- the danger of not spelling something out is a miscommunication due to typical-mind-type hidden assumptions (on the part of either person in the conversation). The key is to keep the level of detail below the "excruciating" threshold.

Comment author: MendelSchmiedekamp 21 May 2009 01:00:44PM 2 points [-]

Assuming your primary goal is to communicate the error then being able to communicate the reasons for the classification of the error to yourself may be of some use, but that is not equivalent to successfully communicating the reasoning to the person who has committed the error.

On the other hand, if your primary goal is to signal status, then inconspicuously failing to communicate your reasons is good, as long as others do not point out your own errors. Which makes self-checking closer to sufficient.

Admittedly, that doesn't mean that this post's obligatory explianation is the best way to communicate reasoning either. Reliably successful communication is a hard problem, which means applying serious rationality to it.

Comment author: hirvinen 28 May 2009 03:48:17PM 0 points [-]

sometimes it really is pretty obvious that a particular error has been committed

The degree or lack of obviousness is a fact about the reader's mind, not about the error.

Comment author: conchis 28 May 2009 06:02:02PM 0 points [-]

Of course. By "pretty obvious" I meant "obvious to most readers" (obviously! :P).