Karl Popper came up with the idea in the 1930's that scientists should attempt to falsify their hypotheses rather than to verify them. The basic reasoning is that while you cannot prove a hypothesis to be true by finding a number of different confirming instances (though confirming instances do make you more confident in the truth), you can prove a hypothesis to be false by finding one valid counter-example.
Now Orin Thomas writes at WindowsITPro that you’ve probably diagnosed hundreds, if not thousands, of technical problems in your career and Popper's insights can serve as a valuable guide to avoid a couple of hours chasing solutions that turn out to be an incorrect answer. According to Thomas when troubleshooting a technical problem many of us “race ahead” and use our intuition to reach a hypothesis as to a possible cause before we’ve had time to assess the available body of evidence. "When we use our intuition to solve a problem, we look for things that confirm the conclusion. If we find something that confirms that conclusion, we become even more certain of that conclusion. Most people also unconsciously ignore obvious data that would disprove their incorrect hypothesis because the first reaction to a conclusion reached at through intuition is to try and confirm it rather than refute it."
Thomas says that the idea behind using a falsificationist method is to treat your initial conclusions about a complex troubleshooting problem as untrustworthy and rather than look for something to confirm what you think might have happened, try to figure out what evidence would disprove that conclusion. "Trying to disprove your conclusions may not give you the correct answer right away, but at least you won’t spend a couple of hours chasing what turns out to be an incorrect answer."
(Score: 2) by tibman on Monday May 25 2015, @06:29PM
Most of the time it is a failure to apply Diax's Rake [wikia.com] : )
SN won't survive on lurkers alone. Write comments.