Not saying it's a good idea. In fact, I watched someone on twitter debugging code. When the application errored out, he regenerated the code, including the issue in the prompt. Something else failed, the prompt was updated, and code regenerated. Now that of course was for visible errors.
When the person building the application doesn't know or care, the application will still be deployed.
I recently had the pleasure of reviewing AI-generated Ruby code at work. It was so nonsensical and couldn't manage to get basic map and reduce right. I didn't initially know it was AI generated, and I was at a loss of words regarding what I should write as feedback.
Something needs to be done. It should be uncontroversial to require solid understanding of fundamentals from software professionals, yet here we are discrediting knowledge by calling such things "gatekeeping." It's reckless behavior as the industry is hellbent on hoarding as much personal information as it possibly can. Information that any responsible professional should be working to keep secure at the very least.
When the person building the application doesn't know or care, the application will still be deployed.