Predictions like these always overlook where 90% of the software lifecycle really takes place: legacy code. Code-generators-for-the-masses my be able to create

Predictions like these always overlook where 90% of the software lifecycle really takes place: legacy code. Code-generators-for-the-masses my be able to create new code but it can't modify, extend, repair, or maintain old code. To change an app, all code generators require that you modify the app's configuration and then generate all new code. That works fine if you know what part of the configuration caused the failure. Otherwise the generator will continue to generate bad code and you're forever screwed. Anyone who generates code from high level specs but doesn't know how the code executes on the computer will be mystified by a misbehaving app or by error messages, and unable to diagnose, must less fix, problems that arise. Think of a car that's designed and built by automation. If the automaton has no idea how to fix the car when a part fails during its lifetime, the only way it can repair the car is throw the whole car away and generate a new one. But with the problem undiagnosed, the same bad part will cause the second car to fail in the same way the first one did. The software life cycle is about much more than writing new code.