4 ms·
That part was probably more about using the scientific method in personal life, I got a bit off track. But to answer you, the idea is that you should have a bel
by automatoney 8y ago
That part was probably more about using the scientific method in personal life, I got a bit off track. But to answer you, the idea is that you should have a belief beforehand, and the experiment is how you test beliefs. The experiment should be designed to falsify a specific idea. Like say for example your code doesn't work. You have to have an idea of where it could be broken in order to test that belief. So you know there's a method with complex decisions, and it should call foo, but you believe that it isn't. To test this you throw a print at the top of foo, and see what happens. The belief is necessary to create the experiment - you won't make efficient progress if you put print statements after every line. The experiment is designed to differentiate between "this idea wrong" and "this idea is probably right".
- analog31 8y agoI suppose in the case of programming, there should be a belief in what a function does, because somebody wrote the function in the first place. I'm thinking about my own work, in areas such as physics and electronics. On one fine day, I measured the characteristics of about 100 Zener diodes, to inform a design decision with about 3 or 4 possible outcomes. I don't see where pinning myself down to a particular opinion of the expected outcome before making the measurement would have changed the outcome.