3 ms·
For many professional programmers, the rigorous stage of their education never got to the techniques for proving the correctness of programs, or even a realizat
by mannykannot 12y ago
For many professional programmers, the rigorous stage of their education never got to the techniques for proving the correctness of programs, or even a realization that such techniques exist. We see this in the discussion of design issues, where informal arguments based on rules-of-thumb, reasonableness, best practices and aphorisms (e.g. "code smells") predominate. There is a tendency for dogmatism to arise in this environment ("thou shalt never write the same expression more than once - always factor it into a function.") (dogmatic thinking is probably confined to a small minority, but because they are vocal, they tend to dominate the discussion.)
I am not one of those who think a transition to formal methods is feasible, let alone that it would solve software's problems. I am also aware that many programmers are effective in putting their general critical thinking and reasoning skills to work in writing correct code (this is one of the reasons why some people without any formal CS education can become excellent programmers.) Nevertheless, and speaking only from my own experience, I think some exposure to more rigorous approaches would help programmers tackle tricky problems, such as those that arise in matters of concurrency or security.