I hope you aren't missing the point. My position is similar to the author. I WILL take responsibility for the code I push to production, and rather than input a prompt and roll the dice on the outcome, I am strategic in my prompts, ensuring the LLM has the right context each time I I voke it, some of that context being accurate descriptions of what I want built, and I am in charge of ensuring it has been properly vetted. Many times I will erase what the LLM has written and redo it, by myself depending on the situation.
Replace "LLM" with "IDE" and re-read. The LLM is another tool. Of course tools can't be held responsible, the person wielding the tool is.
You will be cursed with years of calling every pharmacy in town once a month to figure out which one has your medication in stock this time, and once you figure that out, you stay on the phone with them until you walk into the store to pick it up so they don't give it to someone else.
I don't know about other property seized as evidence, but my car costs a nontrivial amount for me to own and maintain, and it's critical for my way of life. Losing my car for even a couple of days would be a very serious disruption of my life.
Reminds me when my daughter made her Roblox account. They had some rule "don't use your real name" but they never asked her for her real name, so couldn't validate. They would arbitrarily fail a lot of chosen usernames that were made up fake names.
When she tried a variation of "Taylor Swift" it worked fine.
Those rules sound more like they were developed by admins that don't know proper security and so they add complicated rules to feel like they are improving security.
The only password rule that needs to exist is "use something you've never used before". That really does make it difficult for most users though.