TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Sonus silentii fallacy

34 点作者 pud超过 11 年前

15 条评论

itafroma超过 11 年前
The fallacy the author is thinking of is called <i>argumentum e silentio</i>, or the argument from silence. Academically, arguments of the form &quot;well, X civilization is known for meticulous record-keeping and they make no mention of Y, therefore Y must not have happened&quot; would be good examples of arguments from silence.<p>In this instance however, it&#x27;d be of the form, &quot;if our product was defective, our customers would speak up. We haven&#x27;t heard anything from our customers about it, therefore our product is not defective.&quot;<p>The author correctly points out that this formally follows the modus tollens format:<p><pre><code> A: Our products are defective B: Customers are complaining to us P1. A → B P2. ~B ------ C: ~A </code></pre> This is a valid[1] argument: assuming the premises P1 and P2 are true, C necessarily follows. The fault in logic comes from P1 not being true: it is not necessarily the case that customers would complain to the company if the product was defective. Since P1 is false, the argument is unsound[2] and thus ~A (our products are not defective) is not necessarily true.<p>However, it&#x27;s important to point out that one can still inductively[3] conclude ~A is <i>likely</i> to be true, just not <i>necessarily</i> true. That is:<p><pre><code> P1. Based on past evidence, our products being defective likely means customers would speak up about it. P2. Our customers haven&#x27;t complained to us ----- C: Our products are probably not defective. </code></pre> This is a perfectly fine inductive argument. The company, should they be claiming to make this argument, would have to be amenable to be proven wrong: while it may be unlikely that customers would remain silent if their product was defective, it&#x27;s certainly possible.<p>[1]: <a href="https://en.wikipedia.org/wiki/Validity" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Validity</a><p>[2]: <a href="https://en.wikipedia.org/wiki/Soundness" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Soundness</a><p>[3]: <a href="https://en.wikipedia.org/wiki/Inductive_reasoning" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Inductive_reasoning</a>
评论 #6473890 未加载
jloughry超过 11 年前
In the second World War, bombers returning from missions over Germany were carefully examined for battle damage and the locations of bullet holes mapped. Armour plating is heavy and cuts into the planes&#x27; useful range and load---where should it be placed? Abraham Wald suggested putting armour plate over places where no bullet hole had ever been observed, because those were the vulnerable spots. Planes shot in those locations never returned to be counted.<p>It&#x27;s called the problem of non-ignorable non-response.
评论 #6473137 未加载
wrs超过 11 年前
I worked on the first Microsoft product to ship with the &quot;sorry, the program has crashed, please report it&quot; dialog box. (MSN Explorer, if you&#x27;re curious.) Very soon I had thousands of reports of crashes in a system service that were clearly not the fault of our app. I took the reports to the other team to get the problem fixed, and their initial response was &quot;no users have reported it, and it&#x27;s never happened in our test lab, so we&#x27;ll make it a low-priority bug&quot;. (!!!)<p>Thank goodness for the internet...your app&#x2F;device can report its own problems rather than waiting for your users to do it.<p>(BTW: MS product teams did quickly regroup to prioritize actual crash reports over the test lab.)
评论 #6473732 未加载
StavrosK超过 11 年前
Absence of evidence <i>is</i> evidence of absence (it&#x27;s not proof of absence). If there is no evidence that anyone is unhappy with the product, it is strictly better than if there <i>is</i> evidence that some people are unhappy (obviously). So, the &quot;evidence of absence&quot; one isn&#x27;t a fallacy, really.<p>Hell, the modus tollens is a valid argument form. If X, then Y. No Y, therefore no X (but this isn&#x27;t strictly &quot;evidence of absence&quot;).
评论 #6473274 未加载
评论 #6473395 未加载
erehweb超过 11 年前
Going from &quot;nobody has complained&quot; to &quot;the customers are happy&quot; does not seem too much of a stretch, particularly for an expensive unit. Granted, it doesn&#x27;t logically follow, but I would class this as a reasonable deduction from evidence rather than a fallacy. Note also that it&#x27;s self-correcting - once one person complains, the company can&#x27;t use that defense any more.
codex超过 11 年前
Unfortunately one cannot assume the opposite either: that just because your unit broke, others have broken, or many others have broken. You buy thousands of things in your lifetime; odds are that at least one will suffer some kind of freak failure, or even repeated failures.<p>In this case the manufacturer is in a position to have more evidence, at least in principle, even if they might be inclined to ignore it.<p>In my own experience, if Google didn&#x27;t turn up other instances of my problem, the issue was extremely rare or caused by some unique quirk in my environment.
noonespecial超过 11 年前
<i>I own a relatively expensive piece of electronic equipment that keeps breaking.<p>I corresponded with someone who works for the manufacturer. His response to me was (paraphrased), “we’ve sold thousands of these units and nobody else has complained. Therefore, our product must be good.”</i><p>I&#x27;ve never quite understood the logic behind this thinking on the part of product manufacturers. The product has already disappointed the customer on multiple occasions, but the customer is <i>still</i> willing to give the product another chance in the form of a repair or replacement; and the manufacturers first impulse is <i>that rotten customer is stealing from us, treat him like some kind of thief</i>.<p>They&#x27;re about to lose that customer (and everyone he knows who asks him for a recommendation) <i>forever</i>. Send him a replacement. Send two. For bonus points, pay for him to ship the defective one back for detailed analysis of what was going wrong.
评论 #6473630 未加载
评论 #6473504 未加载
pjdorrell超过 11 年前
A variation on this is:<p>* Our Internal Revenue Collection website must be really good, because no one ever complains about it, even though we have a conspicuous link to the complaints form on every page.<p>* Why would anyone ever hesitate to make a complaint to the Ministry of Internal Revenue Collection if they felt they had something to say?
greenyoda超过 11 年前
It&#x27;s also possible (and perhaps more likely) that all the other customers received products that work OK, but there was some kind of rare manufacturing defect in the device the author bought (e.g., an out-of-tolerance part or a bad trace on a circuit board). Of course, the manufacturer should have recognized that as a possibility. This kind of problem shows up a lot with cars, where you can have a &quot;lemon&quot; that has recurring problems.
评论 #6473381 未加载
prof_hobart超过 11 年前
Is it the same unit that keeps breaking, or do they keep sending replacements and they all keep breaking?<p>If it&#x27;s the former, then the story seems to miss the rather critical point that even if they were 100% certain that every other user was happy, that&#x27;s irrelevant to whether he&#x27;s got a faulty unit.<p>However good your quality control is, eventually a faulty one is going to fall through the net, so the fact that a thousand or a million other people have ones that didn&#x27;t go wrong does&#x27;t help the one person who&#x27;s unit did.<p>Of course, if he claims to have had multiple faulty units, and no one else has ever reported any, that&#x27;s a different matter.
mathattack超过 11 年前
This seems to me to be more like <i>Supportus Lazicus</i>. Many support organizations are purposefully understaffed, so you have to mathematically prove that there&#x27;s a problem to get through the noise. For small ticket items it&#x27;s very hard to beat this. Many large ticket software firms have this problem too. That&#x27;s why you need to negotiate an out in the contract, so you can call the salesman and say, &quot;Your competitor is coming in for a demo in forty five minutes. I&#x27;m not sure if this is a bug or not, can you look into it for me?&quot; You&#x27;ll get a response within 30 mins.
gcb1超过 11 年前
&quot;but 100% of the access are using IE6. why should we add support for another browser?&quot;
kineticfocus超过 11 年前
A Priori rationalization based on Argumentum ad Ignorantiam. Conflated with A Fortiori of the evidence. (Just my guess)<p>edit: could also be labeled a non sequitur.
fluxon超过 11 年前
<i>&quot;I own a relatively expensive piece of electronic equipment that keeps breaking.&quot;</i><p>Underconstrained problem set: no $ figure, class of product, mfg name, or indication of who repaired it. Without <i>any</i> specifics, it&#x27;s difficult to analyze the manufacturer&#x27;s response in its true context.
cstrat超过 11 年前
Reading the title I attributed the faulty electronics as being a Sonos product.
评论 #6475525 未加载