Congrats and welcome to the wonderful world of ports.

I would say yes, verifying that the code not only does what you expect but also doesn't do anything of the things you do not expect, is the main bottleneck.

That is: do-all-the-things, please, and don't-do-all-the-non-things, as well.

Ideally, one can reason through their application at a high-level and have a "spec" or specification that the LLM can build from and check against.

You can also have the LLM go back through and tell you about any vulnerabilities you need to address before shipping.

I don't know exactly what you are shipping, but in general: never give the LLM root access or command-line access in a deployed app. Give it the minimal permissions necessary to accomplish its work/role. Pin versions [if you're working with version 5, explicitly say that, rather than just using the "latest" one since that's a moving target].

Some things are not obvious until deployed to a live environment, so do thorough testing. You can have an LLM generate test cases and run a "test suite" to check your code does all-the-things and none-of-the-non-things [undesirable outcomes] this way.

But again, when you have many moving gears finally coming together in a product, in a real, online environment, your best bet is doing lots of testing first to give yourself confidence you've caught most of the edge-cases, and that there are no "catastrophic" edge-cases lurking, unaccounted for.

If you still have any specific questions or want to zoom in on any aspect of software creation, please ask us

[dead]