Today, I want to share a few paragraphs from the beginning of Code Complete. It's a useful look at the heuristic metaphors that we use in programming every day. I think it shows how deliberate, useful mental shortcuts over time can dramatically increase our productivity. Let me know what you thing of it.
Metaphors contribute to a greater understanding of software-development issues in the same way that they contribute to a greater understanding of scientific questions. In his 1973 Turing Award lecture, Charles Bachman described the change from the prevailing earth-centered view of the universe to a sun-centered view. Ptolemy's earthcentered model had lasted without serious challenge for 1400 years. Then in 1543, Copernicus introduced a heliocentric theory, the idea that the sun rather than the earth was the center of the universe. This change in mental models led ultimately to the discovery of new planets, the reclassification of the moon as a satellite rather than as a planet, and a different understanding of humankind's place in the universe.
Today it's difficult to imagine anyone thinking that the sun moves around the earth.
Similarly, it's difficult to imagine a programmer thinking that all data could be viewed
as a sequential stream of cards. In both cases, once the old theory has been discarded, it
seems incredible that anyone ever believed it at all. More fantastically, people who
believed the old theory thought the new theory was just as ridiculous then as you think
the old theory is now.
It's tempting to trivialize the power of metaphors. To each of the earlier examples, the natural response is to say, "Well, of course the right metaphor is more useful. The other metaphor was wrong!" Though that's a natural reaction, it's simplistic. The history of science isn't a series of switches from the "wrong" metaphor to the "right" one. It's a series of changes from "worse" metaphors to "better" ones, from less inclusive to more inclusive, from suggestive in one area to suggestive in another.