3 ms·
The source cited for "it's worth looking up whose blog this is" is almost entirely dedicated to the proposition that he's a bad person with nothing whatsoever a
by Natsu 4y ago
The source cited for "it's worth looking up whose blog this is" is almost entirely dedicated to the proposition that he's a bad person with nothing whatsoever about his argument about the Flynn effect.
You're just kinda digging the hole deeper at this point, man. It's not even about time management, which is what people usually cite for this sort of epistemic learned helplessness, because you could've just saved your time by not even replying if that was what you were after.
- Dylan16807 4y ago> The source cited for "it's worth looking up whose blog this is" is almost entirely dedicated to the proposition that he's a bad person with nothing whatsoever about his argument about the Flynn effect. Because it's useful to know if someone is wrong a lot, just like it's useful to know a clock is broken, and you don't need any fallacies for that. For example, if someone misuses citations a lot, it's good to tell people that, even if you don't say anything about the particular subject. I get it that you don't like this attack on the person rather than the post. But it's not committing the fallacy of saying "it's him therefore it's wrong". The fallacy you describe about broken clocks is not happening. Saying either "it's him therefore it's weaker" or "it's him therefore it's useless" would not commit that fallacy. If a clock is sometimes broken then "weaker" is correct, and if a clock is always broken then "useless" is correct. And the impression I got was very much "it's him therefore it's weaker". And it's not an irrelevant attack. Attacks on the way he constructs arguments are relevant to all arguments he makes. You can't just claim it's a specific fallacy and then talk about how it's bad rhetoric in general as support of that claim. > You're just kinda digging the hole deeper at this point, man. It's not even about time management, which is what people usually cite for this sort of epistemic learned helplessness, because you could've just saved your time by not even replying if that was what you were after. Don't be an asshole, and I never said I was here to save time. I'm here to say that a couple accusations of specific fallacies are wrong. See also this very nice comment: https://news.ycombinator.com/item?id=35520629 https://news.ycombinator.com/item?id=35520629
- Natsu 4y agoThe whole point of the fallacy is that this other stuff isn't relevant to the truth of the argument, and it does nothing to inform us about the argument. You can't figure out the time by arguing over broken clocks. And you're only interested in staying on message here, not about whether these things are even true or not.
- Dylan16807 4y agoIf someone is trying to use a broken clock as a source, it's valuable to tell them it's broken. The clock doesn't tell you if they're right or not. I agree here, see me agreeing! That's the part that would be a fallacy! But knowing that the clock is broken means you know that any conclusions based on the clock contain zero information. They might be right, but only by accident. So you should completely reject the argument, without completely rejecting the result. To make that even more explicit: An argument and the conclusion of that argument are different things. The bar for rejecting an argument is lower than the bar for rejecting its conclusion. And the bar for being extra skeptical is even lower. The fallacy you're describing happens when you reject the conclusion. It does not happen when you reject the argument.
- Natsu 4y agoIf someone tells you that someone is wrong and yet they can't explain how, they're a broken clock.