3 ms·
That post might have been wrong, but that doesn't make it dumb. When something is wrong and a waste of time (in the sense that the author should have known bet
by DenisM 7y ago
That post might have been wrong, but that doesn't make it dumb.
When something is wrong and a waste of time (in the sense that the author should have known better) that's dumb.
When something is wrong but not obviously so, and it helps us summarize existing opinions, or guide exploration, and/or otherwise advances the state of our understanding, it's not dumb.
For example, a wrong scientific hypothesis or a wrong startup thesis is not always dumb; they are only dumb when the author should have known better, but chose not to do the homework. Incidentally, this might be the easiest way to fail a YC interview - demonstrate that you think the homework is beneath you.
It's ok to be wrong, just make sure it's "the right kind of wrong".
- ineedasername 7y agoAbsolutely. Something can be wrong, but constructively so, adding to the discourse in a positive way by still raising valid points even if it draws conclusions that don't quite follow from those points. It's why I often find myself upvoting things I might really disagree with because I nonetheless believe it adds to the conversation in an interesting and constructive way. And conversely, why I sometimes downvote things I agree with when the comment is shallow, snarky, antagonistic, or dismissive of other possible views.