How Does Veritula Work?
Showing only those parts of the discussion which lead to #2097.
See full discussion·See most recent related ideasLog in or sign up to participate in this discussion.
With an account, you can revise, criticize, and comment on ideas.@dennis-hackethal you have regularly pointed out to me that it’s a mistake to assign strengths or weaknesses to arguments—for example, in #1809 and #1927. I’d love to get to the bottom of that.
On one hand, I see what you mean. A criticism can either be counter-criticized or it can be an unresolved error. If it’s a bad criticism, you quickly counter it—say, by clarifying why it’s irrelevant—and move on.
I also see why talking about a “gradient” or comparative strength between arguments is problematic: there’s no objective criterion to measure them against. We can only say one theory is better than another when both attempt to explain the same phenomenon—then we can evaluate them using properties such as hard-to-varyness and other criteria Deutsch describes. (We can get into that if you’d like, though I don’t think that’s our main disagreement.). But this comparison doesn’t apply when we’re dealing with very different criticisms of a single idea, because there’s no common standard to measure them against. Comparing their “strength” becomes arbitrary.
However, I still think there are good and bad criticisms, just as there are good and bad explanations (following Deutsch’s distinction: for instance, bad explanations are easy to vary or point to authorities to justify themselves rather than offering a hard-to-vary account of how and why something works). While I could simply counter-criticize bad criticisms and move on, there’s also the matter of efficiency and opportunity cost: I don’t want to waste time repeatedly countering poor criticisms, or worse, get stuck in circular debates with people who don’t recognize that some arguments aren’t good criticisms at all. I’d rather focus my attention on good criticisms.
To clarify what I mean, here’s an excerpt from my book:
The most important principle to remember while criticizing is: Criticize, don’t defend or attack. Good explanations invite criticism of their intrinsic content—whether the explanation itself works, solves the problem, and avoids worse side effects. Bad explanations, by contrast, deflect criticism onto irrelevant, extrinsic properties such as authority or track record—e.g., “this is the method that successful company X uses,” “I believe strongly in this approach,” or “it’s coming from person Y, so it’s worthless.”
That kind of “criticism” isn’t real criticism at all. It’s just attacking or defending. And when we play that game, the explanation itself stays untouched and stagnant. The idea doesn’t get scrutinized or improved—it only gets shielded or dismissed for irrelevant reasons.
That being said, I agree with the points you brought up in #2061, namely that there can be no positive arguments for an idea. By extension, if Veritula would require a specific format or mode of criticism, we’d fall into the very error Popper warns about with the Myth of the Framework—the mistaken belief that criticism requires a shared framework or language. So, Veritula should functionally remain as it is. At most, you might consider adding guidelines on what constitutes good versus poor criticism, so that critics can improve their skills. But I agree: the person who created the idea should remain solely responsible for addressing the criticisms they receive, not dismissing them as “bad” and moving on.
Tagging @bart-vanderhaegen because he and I have discussed this at length—in fact, I got the defending/attacking framing from him.
There’s another issue with disregarding ‘small’/‘weak’ criticisms: some criticisms may look small at first, but as you investigate, you realize they’re actually a big deal.
I realized this the other day on the topic of macOS UI bugs during a Twitter space. Somebody said that many of the issues I had pointed out with the new Tahoe OS were just minor UI glitches (in other words: ‘weak criticisms’). But then somebody else pointed out that those are still worrisome because severe security holes, like being able to bypass authentication, have presented as minor UI glitches in the past!
I agree with the premise that small does not mean insignificant. My current view is that the only meaningful dichotomy is good vs. bad. I may have used labels like weaker or stronger, smaller or bigger, minor or major in the past, but I now see that was a mistake—they have no place when judging a criticism. So in this case, I don’t think the criticism applies because we’re not in disagreement.