3 ms·
> The latter, not surprisingly, turned programming from an intuitive activity into a formal one in which the program is derived by symbolic manipulation from it
by AnimalMuppet 7y ago
> The latter, not surprisingly, turned programming from an intuitive activity into a formal one in which the program is derived by symbolic manipulation from its functional specification and the chosen form of correctness proof.
> The idea of a formal design discipline is often rejected on account of vague cultural/philosophical condemnations such as ”stifling creativity”; this is more pronounced in the Anglo-Saxon world where a romantic vision of ”the humanities” in fact idealizes technical incompetence. Another aspect of that same trait is the cult of iterative design.
> Industry suffers from the managerial dogma that for the sake of stability and continuity, the company should be independent of the competence of individual employees. Hence industry rejects any methodological proposal that can be viewed as making intellectual demands on its work force. Since in the US the influence of industry is more pervasive than elsewhere, the above dogma hurts American computing science most. The moral of this sad part of the story is that as long as computing science is not allowed to save the computer industry, we had better see to it that the computer industry does not kill computing science.
Typical Dijkstra. You do it his way or you're not only wrong, but also stupid. But "his way" is to have a correct formal specification that you can operate on using mathematical logic. We have learned, from bitter experience, that that's asking quite a lot, and even when you can get it, it's a recipe for building systems that are obsolete on the day they are completed. But Dijkstra is content to pronounce the system produced to be "correct". That approach may cut it in academia, but in the real world it has been tried and found to be sorely wanting.
Then you get to aspects that really are a combination of art and science. Would Dijkstra's approach have produced, say, the iPhone user interface? I strongly doubt it.
- rramadass 7y agoI used to think like you, until one day i read D.L.Parnas' paper "A Rational Design Process: How and Why to Fake it" (http://users.ece.utexas.edu/~perry/education/SE-Intro/fakeit.pdf http://users.ece.utexas.edu/~perry/education/SE-Intro/fakeit...). I then could understand Dijkstra's pov. He was advocating for rigor in Programming and that the very effort reqd. to hew to his ideal would result in better Software. That is the gist of his argument. Unfortunately, Humans are heuristic, pattern-matching, infinitely adaptable organisms and hence absolute rigor is very difficult. The fact that programming languages are so evolved that one can easily code-up any incoherent stream of consciousness and still have the system-as-a-whole work in some fashion is what has contributed to both the boom (anybody can contribute) and mess (quality sorely lacking) in the industry. PS: Never ever dismiss pioneers like Dijkstra, Hoare, Wirth and others offhand. They built up the Fundamental Theory, Science and Tools which directly led to today's Computer Industry and its effect on Society.