This my technique- test the output, make sure it works (in the sense of outputs) the way I want. Test the input edge cases, move on. Occasionally when I can't get it to do what I want the llm suggests things like logging of output between functions etc- in which case they get added, but at the end I ask it to take out all the logging and make the code more concise.

And sometimes it breaks in ways I can't fix - so rolling back or picking a new patch from a know break point becomes important.

16 hours for my first azure pipeline, auto-updates from code to prod, static app including setting up git, vscode, node, azure creds etc. I chose a stack I have never seen at work (mostly see AWS) and I am not a coder. Last code was Pascal in the 1980s.

3rd app took 4 hours.

Built things I have wanted for 30 years.

But yes- no code understanding, brute force.