Karl Popper claimed, with some right, that the interesting thing in science isn't what we can absolutely prove, but what we can (in principle) disprove. The reason for this is that we can (probably) not find any ultimate truths, but only find special cases of then.
An example of what was once believed to be an absolute truth but is now regarded as a special case is Newtonian Mechanics. It works quite well outside steep gravity wells, at low acceleration and at low speeds, but starts to break down as soon as we achieve a speed closing in on light-speed.
A good cognitive model is medicine, up until the late 70s, early 80s, where there wasn't much investigation into the "how" and "why" of medications (surgical procedures were, for the large part, fairly well understood), but rather a wild testing of assorted substances to see how they worked.
The main difference we can see in their workings is by construction examples. Let's look at a rain dance. I don't know if there's actually any tribe on Earth who perform these, but it's well-enough illustrated in comics and on film for it to be a decent illustration of principles.
The medicine man looks at the sky, to ee if the portents for a rain dance is good or if petitioning the Rain God would bring down wrath on the community. He can, from experience, tell us that the signs are good. So, he takes his hand drum, paints his upper body with red and white paint and goes to the ceremonial stage to perform this essential rain dance.
After almost forty-five minutes of energetic dancing and drumming, our medicine man is rewarded by rain.
Now, one could wonder about cause and effect. Is there any cause and effect oinvolved? But at that point, we'd be practicing science, not technology. We're only interested in end results (and what steps we need to take to get there).
One modern field, where technology seems to be well on the way to being entrenched is in software development. Especially in the developing and refining development processes (cf. "Extreme Programming", "UML diagramming" and similar), where there's no real trace of science in the end result. there may well have been in the design process, but since we can't see any direct traces of it, we are left to wonder.
After some more observations, we start seeing another pattern. Whenever the omens are good for rain dancing, there's a layer of thin clouds being blown towards the village and they're moving "up-hill" (in the direcftion where a person would've been moving up-hill, ahd they been taking the same route on the ground). So, we form another hypothesis, "the rain dance causes vibrations in the thickened air, causing rain to fall".
We can now test this hypothesis. We choose to wait until there's good omens and stop the medicine man just before the dancing takes place. Rain falls. Uh-oh, seems as if the rain dance possibly wasn't strictly speaking necessary. So, we chaneg our whole hypothetical model from "rain dance causes rain" to "the medicine man instictively can tell when rain is abouit to start from looking at clouds".
From this model, it should be fairly easy to deduce that clouds are water suspended in air and that the elevation gained from the cloud being pushed up-hill by the sqme wind that causes the clouds to move. Some more experimentation would show us that cool air can contain less moisture than hot adn here we should be able to see acceleration of rain-drop formation caused by having suitable drop seeds in the cloud.
It can be bad, though, when technological inquiry is mistaken for scientific inquiry.
This is one of Ingvar's essays
By: Thomas Elam
2008-11-07 11:20
Ingvar, I really liked your science & technology essay.