Re:Automating programming: AI is transforming the coding of ...
by ChrisMarshallNY on Friday July 09, 2021 @05:20PM
(#27788660)
The thing that so many folks seem to forget about programming, is that the most problematic part of the whole thing is the Requirements Phase. That's where the most serious problems occur, and they are often in the form of ticking time bombs that explode while the project is well underway. A good implementation team knows how to stop assuming, and get more information from the requirements authors.
No matter how "smart" the implementation process is, we have the principle of "GIGO" (Garbage In; Garbage Out). Automated implementation has the potential to be a garbage multiplier.
There will always be a need for highly specific, accurate and detailed specifications. If a machine does the work, and makes assumptions, then that means the input needs to be of even higher quality than we see nowadays (See "GIGO," above).
I see the evolution of "Requirement Specification Languages," which, I suspect, will look an awful lot like code.
No matter how "smart" the implementation process is, we have the principle of "GIGO" (Garbage In; Garbage Out). Automated implementation has the potential to be a garbage multiplier.
There will always be a need for highly specific, accurate and detailed specifications. If a machine does the work, and makes assumptions, then that means the input needs to be of even higher quality than we see nowadays (See "GIGO," above).
I see the evolution of "Requirement Specification Languages," which, I suspect, will look an awful lot like code.