Re:Programmers who want to change how we code before catastr...
by catnaroek on Wednesday September 27, 2017 @08:36PM
(#15353574)
> And you have the little problem of (correctly) creating the formal spec.
How on Earth did we end up putting people who can't write down precisely what they want in charge of programming machines that do exactly what you tell them to?
Re:Programmers who want to change how we code before catastr...
by perl4ever on Wednesday September 27, 2017 @09:34PM
(#15353845)
I was just told today that gathering requirements is not my job, it's the PM's. But they are swamped in administrative minutiae, and all too often the only person who knows how something worked has quit anyway. So in sum "no spec, no spec, you're the spec!"
Re:Programmers who want to change how we code before catastr...
by kmicklas on Thursday September 28, 2017 @11:40AM
(#15357931)
> But it's inadequate for the larger problem, of whether the operation is the correct one.
Huh? Types (of the sufficiently advanced kind) are one way of specifying behavior in the same sense as TLA+ and other models. The difference is that type theory provides a coherent story for how to form entire systems like this in a composable manner. Traditional modeling/spec languages, not so much.
Re:Programmers who want to change how we code before catastr...
by hwayne on Thursday September 28, 2017 @06:32PM
(#15361333)
What are some good examples of complex system properties you've seen verified with sufficiently advanced types?
Formal methods can ensure that the code matches a formally written spec, for all the aspects of the code that are covered by the formal method. Note well: That's not all aspects of the code. And you have the little problem of (correctly) creating the formal spec. This move the problem up a layer, but the problem doesn't go away.
Even given a formal spec, though, it's my impression that formal methods are s l o w. Does anyone have data on this?