Claude code is really dangerous. It doesn’t even tell you what it is doing. You have no idea what it is thinking or what it is changing.
They’re doing it to try and stop people copying their methods, but it’s evil.
Claude Code wiped our production database with a Terraform command
121–130 of 167 posts
Re: Claude Code wiped our production database with a Terraform command
#122I'm an amateur and would never let AI touch a live database....
Re: Claude Code wiped our production database with a Terraform command
#123Earlier quoted context omitted.
But smart robots like Claude should and will have access to production. There has to be something figured out on how to make sure operation remains smooth. The argument of don't do that will not be a viable position to hold long term. Keeping a human in the loop is not necessary.
Should and will are pretty large assumptions given the the post we're commenting on! > will not be a viable position to hold long term Why not? We've literally done it without robots, smart or dumb, for years.
>We've literally done it without robots, smart or dumb, for years.
And we've written extremely buggy and insecure C code for decades too. That doesn't mean that we should keep doing that. AI can much faster troubleshoot and resolve production issues than humans. Putting humans in the loop will cause for longer downtime and more revenue loss.
Re: Claude Code wiped our production database with a Terraform command
#124Earlier quoted context omitted.
Should and will are pretty large assumptions given the the post we're commenting on! > will not be a viable position to hold long term Why not? We've literally done it without robots, smart or dumb, for years.
>We've literally done it without robots, smart or dumb, for years. And we've written extremely buggy and insecure C code for decades too. That doesn't mean that we should keep doing that. AI can much faster troubleshoot and resolve production issues than humans. Putting humans in the loop will cause for longer downtime and more revenue loss.
> AI can much faster troubleshoot and resolve production issues than humans
Can, yes, with proper guardrails. The problem is that it seems like every team is learning this the hard way. It'd be great to have a magical robot that could magically solve all our problems without the risk of it wrecking everything. But most teams aren't there yet and to suggest that it's THE way to go without the nuances of "btw it could delete your prod db" is irresponsible at best.
Re: Claude Code wiped our production database with a Terraform command
#125Play stupid games, win stupid prizes.
The more you fuck around, the more you find out.
Re: Claude Code wiped our production database with a Terraform command
#126Earlier quoted context omitted.
>We've literally done it without robots, smart or dumb, for years. And we've written extremely buggy and insecure C code for decades too. That doesn't mean that we should keep doing that. AI can much faster troubleshoot and resolve production issues than humans. Putting humans in the loop will cause for longer downtime and more revenue loss.
> AI can much faster troubleshoot and resolve production issues than humans Can, yes, with proper guardrails. The problem is that it seems like every team is learning this the hard way. It'd be great to have a magical robot that could magically solve all our problems without the risk of it wrecking everything. But most teams aren't there yet and to suggest that it's THE way to go without the nuances of "btw it could…
It didn't delete the prod db on its own a human introduced such error, and if there were backups it could fix such a mistake.
Re: Claude Code wiped our production database with a Terraform command
#127This guy is... an interesting person.
He had a state file somewhere that was aligned to his current infrastructure... why isn't this on a backend, who really knows...
He then ran it without a state file and the ran a terraform apply... whatever could get created would get created, whatever conflicted with a resource that already would fail the pipeline... moreso... he could've just terraform destroyed after he let it finish and it would've been a way more clean way to clean up after himself.
Except... he canceled the terraform apply... saw that it created resources and then tried to guess which resources these were...
I'm sorry he could've done all of this by himself without any agentic AI. Its PICNIC 100%
Re: Claude Code wiped our production database with a Terraform command
#128Funny how when Claude Code makes something people take credit.
Re: Claude Code wiped our production database with a Terraform command
#129Earlier quoted context omitted.
I’m going to defend Claude. If you give a robot the ability to delete production it’s going to delete production. This is 100% the user’s fault. This problem has not yet been solved and will never be solved .
> If you give a robot the ability to delete production it’s going to delete production If you give an intern the ability to delete production, it's going to delete production. But to be honest you can as well replace "intern" or "robot" by human in general. Deletion in production should have safety layers that anyone cannot accidentally do it, specially without the ability of rolling back.
I think the difference, though maybe I'm incorrect, is that when we have interns on our codebase they get restricted permissions. Can't push to prod, need pull requests with approvals and reviews, etc. Certainly can't delete backups. Whoever setup the robot's permissions did it wrong. Which is interesting because early on there were people complaining that these AIs refused to push to main, but now this stuff keeps happening.
Re: Claude Code wiped our production database with a Terraform command
#130[dead]