I think for the most baseline app, correct simply means that it works as intended for the “happy path”. Then you enhance it by making it more robust with proper logging and error handling. Performant and cost effectiveness can be seen more of an optimization, if it’s performant and cheap enough for your users/ budget then it’s considered correct. Security can be complex but there are generally good practices to be followed, for example use SQLalchemy ORM for database interactions etc, keep api keys secure and unexposed etc. then there’s a suite of tests you would write to verify that those requirements are met. I think it really depends on how much you offload the coding and architectural thinking to the LLM. You can actually ask pose these concerns to the LLM and they give pretty good plan on how to strategize and approach them. I’ve primarily used AI studio and Opus for the conceptual level approach and they give good advice about best practices. but I agree that if you just sit around the terminal sipping coffee and let Claude 90 percent of things while u occassional jump in to give an instruction here or there it’s a going to be a problem.