Debate Over Feasibility
Since the term "software engineering" was coined, formal verification has almost always been considered too resource-intensive to be feasible. In complex applications, the difficulty of correctly specifying what the program should do in the first place is also a common source of error. Other methods of software testing are generally employed to try to eliminate bugs and many other factors are considered in the measurement of software quality.
The notion that cost of production of hardware should be a constraint in programming was foreign to Dijkstra. He viewed the cost controls as artifacts that could become excuses and the controls of nature as nonexistent in digital systems, which above the level of circuits guarantee a second, constructed nature.
Until the end of his life, Dijkstra maintained that the central challenges of computing hadn’t been met to his satisfaction, due to an insufficient emphasis on program correctness (though not obviating other requirements, such as maintainability and efficiency).
Read more about this topic: On The Cruelty Of Really Teaching Computer Science
Famous quotes containing the word debate:
“A great deal of unnecessary worry is indulged in by theatregoers trying to understand what Bernard Shaw means. They are not satisfied to listen to a pleasantly written scene in which three or four clever people say clever things, but they need to purse their lips and scowl a little and debate as to whether Shaw meant the lines to be an attack on monogamy as an institution or a plea for manual training in the public school system.”
—Robert Benchley (1889–1945)