With types and comments as a prompt in Go, GPT already produces fairly viable API endpoints for basic CRUD operations.
With some framework to compose various prompted endpoints using the same types and conventions, a junior engineer would be totally unnecessary. They couldn’t code as well, and they couldn’t architect as well as a more experienced engineer doing the prompting.
You could even prompt from a spec and begin iterating upon the outputs, revising each manually or with GPT’s suggestions. Say “take this endpoint and refactor it based on the conventions of this endpoint, and make sure (some logic) accounts for (some potential problem)” and boom, it will probably work okay.
But aren't the devs of the future on GPT right now, half-assing learning to code while getting a fast track education in correcting bugs and architecting?
If this technology evolves to be able to reliably generate working code to a prompt, the entire field of software dev will shift dramatically. Some junior and some senior devs would prove better at meeting deadlines by AI whispering, and others would have to find new career paths.
With some framework to compose various prompted endpoints using the same types and conventions, a junior engineer would be totally unnecessary. They couldn’t code as well, and they couldn’t architect as well as a more experienced engineer doing the prompting.
You could even prompt from a spec and begin iterating upon the outputs, revising each manually or with GPT’s suggestions. Say “take this endpoint and refactor it based on the conventions of this endpoint, and make sure (some logic) accounts for (some potential problem)” and boom, it will probably work okay.