Like painting or architecture, woodworking have a finished state, after that, you just ship it and not worry about it again. whereas in software, everything is so malleable that a rewrite is often going to happen again and again.
If anything, there have to be people in the loop to check balances (write good prompts to generate code and fix them) and take responsibilities for downtime.
One of the most important links of the chain to keep sensitive data safe is to collect less but the motivation behind this is rather small, private or public sector.
I agree with you on this, since we humans want things in a vague form, and it's still very hard for computers to infer insights from those ambiguous requirements. Not very easy to do that by taking derivatives of function compositions.