Meaning that there won't be coders that sit around punching code all day, but rather just generate diagrams and/or feed models with descriptions of systems, and in return get fully functional systems.
5 years? 10 years? 15 years? 20?
You: Here is a bug: [explanation]
GPT: Ok, fixed it!
You: It is still there.
Gpt: Ok, now fixed for real!
You: It is still there...
There's a whole field emerging of prompt engineers, but I think what's desperately missing is good quality integrated UX engineering.
Being able to write a comment and/or a method signature and having an LLM spit out a generated piece of code is kinda cool, but the interface for showing that the code is buggy needs refining. I think that's likely to be quickly showing a test case: given these inputs I'm expecting this output. LLM refactors against all tests, and you iterate together towards the correct solution.
That's one small example of how we can start to think about the future UX that isn't about having a "chat" about your code.
Similar UX thought is needed in other disciplines, it'll be interesting to see how this domain evolves.
It's even more effective when you can limit the domain somewhat to things that can fit in the context window, which eliminates out of date API information.
We will now shortly be able to add visual feedback of the applications into the loop.
Frankly I feel like we are looking at this the wrong way. In the future we might not even have a way to program some things manually. There might be a llm for each device that generates necessary hardware instructions on the fly like today's jit based on natural language or environment. May be there would be a inter llm spec/language that would felicitate cross llm functionality. All short circuiting out the programmers between the user and the utility.
The phase-2 LLM converts the designs to code in either react/flutter (both of which current LLMs are already quite good at) and deploy for a certain set of users. Basically same flow as today minus the engineers. Most of this is even possible today. The only thing saving engineering necks is the context window size which prevents fitting the whole repo in memory. Hopefully we (the programmers) will build our savings to a sustainable level in the next 5 years before signing off on manual coding or finding another thing to do than typing on keyboards to make computers dance.
This is basically science fiction
> This is basically science fiction
Product owners describing requirements in detail! More like fantasy, I think.