The tooling will be pretty interesting.. basically prompts per file and a overlaying diff per prompt..
Focus mostly on the almost functional design of software, with well defined input and output as the most important criteria. Also lots of "meta" tags, that filter the trained in network layers for "fast" code, "secure" code, "minimal working smaple" code by injecting addtional prompts. The trick is to use the prompts as a selection menue for the data variations stored within the Network.
I imagine that a web service could be specified in one file. At the top, a description of the service, including the language it is to be written in and how it will be built and deployed. Then an outline of the endpoints and their functionality.
A builder bot could then ask a series of questions and get permissions such as “can we use X package?”, and then update the specification before performing the build.
