Re:Programming won't be automated, or it already has been
by falcolas on Tuesday July 11, 2017 @09:59AM
(#14744204)
Your comment is being dismissed (and downvoted) pretty thoroughly; but I think there's a grain of truth to it. As has been said by others, we don't get complete specs as it is, and our industry has moved towards "release often and fix the bugs or mistaken assumptions." The only real difference between the output of a NN and a human is the inference of the context to drive those assumptions.
Seeding a NN would be a simple listing of invariants: Headers are at the top of the screen, footers at the bottom, there exists a name field in the page and the datastore; the name field on the page corresponds to the name field in the datastore. Once those invariants are defined, the intermediate product is released to the customers and they directly drive further development of the NN by simply saying "this is not the expected behavior" in some easy drop-down.
I think the biggest hurdle will be that a human's assumptions are going to be more palatable than a NN's assumptions. But once a number of those assumptions are codified (or a statistical preference is determined), this weakness may be effectively mitigated.
This "crowd-sourced" definition of correctness has already been proven - in chatbots. People have been able to coerce chat bots into providing their desired output without touching a line of code.
Seeding a NN would be a simple listing of invariants: Headers are at the top of the screen, footers at the bottom, there exists a name field in the page and the datastore; the name field on the page corresponds to the name field in the datastore. Once those invariants are defined, the intermediate product is released to the customers and they directly drive further development of the NN by simply saying "this is not the expected behavior" in some easy drop-down.
I think the biggest hurdle will be that a human's assumptions are going to be more palatable than a NN's assumptions. But once a number of those assumptions are codified (or a statistical preference is determined), this weakness may be effectively mitigated.
This "crowd-sourced" definition of correctness has already been proven - in chatbots. People have been able to coerce chat bots into providing their desired output without touching a line of code.