Code design? Perhaps. But how are you going to inform a model of every sprint meeting, standup, decision, commit, feature, and spec that is part of an existing product? It's no longer a problem of intelligence or correctness, its a problem of context, and I DON'T mean context window. Imagine onboarding your companies best programmer to a new project - even they will have dozens of questions and need at least a week to make productive input to the project. Even then, they are working with a markedly smaller scope of what the whole project is. How is this process translatable to an LLM? I'm not sure.
The LLM needs vast amounts of training data. And those data needs to have context that goes beyond a simple task and also way beyond a mere description of the end goal.
To just give one example: in a big company, teams will build software differently depending on the relations between teams and people. So basically, you would need to train the LLM based on the company, the "air" or social atmosphere and the code and other things related to it. It's doable but "in a few years" or so is a stretch. Even a few decades seems ambitious.
