|
| ▲ | ktm5j 5 hours ago | parent | next [-] |
| If you read the thread the guy does own up to his actions. He actually sounds like a nice guy who admits he made a mistake. He seems more interested in preventing this kind of thing from being possible than he is interested in dodging blame. I'm happy the guy got his data back. |
|
| ▲ | traderj0e 2 hours ago | parent | prev | next [-] |
| Yeah but it's funnier to blame the AI. And when the "real coders don't use AI" people get pissed off at the joke, you double down instead. |
|
| ▲ | newsoftheday 5 hours ago | parent | prev [-] |
| Does that mean the prompt should include: "...and don't delete my production database."? |
| |
| ▲ | nemomarx 5 hours ago | parent | next [-] | | If the agent didn't have delete permissions, or was sandboxed dying other way from your production database, that would handle it. So not running it that way is a decision someone made | |
| ▲ | bee_rider 5 hours ago | parent | prev | next [-] | | It means people have to read the commands that they are generating before executing them. | |
| ▲ | unregistereddev 5 hours ago | parent | prev | next [-] | | Just in case this isn't hyperbole, no. It means an LLM should not be given that much privilege and that you are responsible for reviewing the tool's output and approving its actions. | |
| ▲ | saghm 4 hours ago | parent | prev [-] | | "But wait, the user probably just meant that I shouldn't delete the database itself. Removing all of the rows in the table is fine" |
|
