|
|
|
HN: The Anti-Science Crowd?
|
|
7 points
by thelettere
1533 days ago
|
|
Why does every post having to do with a scientifically testable question almost invariably have top comments which are purely anecdotal rather than even attempting to point at empirical evidence? This is particularly noticeable in anything having to do with quality of life or lifestyle questions, including the current front page question about anti-depressants. Indeed that relatively upvoted post goes so far as to ask purely for anecdotes - neatly dismissing nearly a century of evidence on the placebo effect, the known wide variance of reactions to any intervention and a million other documented factors that render anecdotes useless. Indeed, as far as HN is concerned, we may as well be in the dark ages, taking a poll on how HNers respond to leeches. On a site users often describe as a kind of oasis from the nonsense perpetuated on the rest of social media, this seems rather baffling and suggests a need for - at minimum - some self-reflection. |
|
The author argued "yes, definitely", but most computer scientists answered "nah, too much work." People fond of $new language like to claim that if just all major software was rewritten in their favorite language life would be so much easier and bugs and security issues would be so much fewer. So you ask, "how do you know?" They answer: "It is obvious." "Have you tested it?" "There is no point, cause it is OBVIOUS!" "But if it is obvious, shouldn't it also be easy to test?" "We have NO TIME for that and if you don't see that $new language is better than $old language you are an IDIOT! Troll someone else!!" Or they'll argue that tests doesn't prove anything cause it depends on the context (like programmer skill, familiarity with $old and $new language, etc). Essentially, their hunch carries more weight than any quantitative data you could ever collect...
So much of software engineering is just shiny new thing after shiny new thing. No one knows whether the shiny new stuff is better than the old stuff or not. Even the book that introduced TDD & DP readily admitted that the project in which the development method was tested failed! Yet everyone adopted TDD because it was so "obvious" it was better.