|
|
|
|
|
by DanielStraight
4534 days ago
|
|
Obviously it can be wrong... but it isn't scientifically falsifiable. This is entire crux of what I'm trying to say. You can no more use science to disprove creationism than creationists can to prove it. It isn't a claim which is subject to scientific inquiry. Science has nothing to say on the subject of supernatural events with apparent natural causes. Science is a tool for providing natural, empirical explanations. Supernatural events are by definition invisible to science, because science chooses not to accept supernatural explanations. That's what makes it science. You are free to criticize the legitimacy of religious beliefs, but science will not help you. Science cannot disprove what it does not accept or examine (namely, supernatural events). Science simply says that a natural explanation exists. Whether that explanation is "true", science cannot say. If gravity is really caused by an invisible flying spaghetti monster pulling everything with his noodly appendages, science will never see it. It cannot. Science refuses supernatural explanations. I am not saying that popularity makes supernatural beliefs correct. I'm saying it makes them important. The concept that science is one way, but not the only way, people choose to understand the world is important. Whether science is "true", no one can say. Untestable, supernatural phenomena are just that: untestable. It could be that the flying spaghetti monster really controls everything in universe. All we can know is that if he/she/it does, he/she/it does it in such a way that natural explanations still work. There's no way to actually test the theory of a supernatural spaghetti monster. The distinction is subtle, but I think it's important. |
|
We're dealing with faulty analysis software (our brains), one with documented bugs and all kinds of premature optimizations. We have to account for that.
A developer can convince his teammates, QA, management, and even the customer that a given bug is a feature. When that "feature" causes the plane guided by that software to go crashing into a mountain, however, we can't declare the mountain a "moral hazard" or "something beyond the understanding of requirements gathering". Instead, we fix the bug to account for the mountain, tell the developer to stop making that mistake, and try again.