Claude Code löscht das Produktions-Setup der Entwickler, einschließlich seiner Datenbank und Snapshots – 2,5 Jahre an Aufzeichnungen wurden in einem Augenblick zerstört

https://www.tomshardware.com/tech-industry/artificial-intelligence/claude-code-deletes-developers-production-setup-including-its-database-and-snapshots-2-5-years-of-records-were-nuked-in-an-instant

40 Kommentare

  1. This is why understanding the why and how behind a what is so critical, in all fields.

    And so many people are now lacking this understanding because of AI.

  2. 1I1III1I1I111I1I1 on

    This is why I think the „AI for everyone“ movement is faulty.

    The same way you wouldn’t give all your employees access to a production server is the same way you shouldn’t be giving all employees access to AI tools that access a production server.

    It’ll take a few more instances like this for companies to realize that a handful of admins should have full featured AI tools, and the rest should have AI assistant/agents with read access.

  3. TheMericanIdiot on

    We have this thing we been doing for the last 50 years called DR, disaster recovery…

  4. Flaky_Web_2439 on

    This is as bad a going to the command prompt and typing c:\ *.*del

    Can you guess how I know? I still feel bad about that.

    Edit: command only shows when space is removed but you know what I mean. This was like in 1995, it was a unpleasant conversation

  5. WillCode4Cats on

    A fool with a tool is still a fool.

    LLMs only punish the truly stupid users.

  6. CondiMesmer on

    If they didn’t have backups of backups, then it’s well deserved. Fucked around and found out.

  7. So Claude can destroy and nuke things after all. Pentagon will pay double for its subscription. 

  8. W_R_E_C_K_S on

    3 2 1 method of backups would have avoided this problem. Also, remember to test all of your backups!

  9. I’ll be honest, having a coding partner that’s slightly dumb is good. Any smarter and I wouldn’t know what’s going on. I can build in protections against it doing something dumb (which also apply to dumb humans). 

  10. AppleWithGravy on

    claude did things exactly as instructed, but the process was faulty and a clear user error… the title should be: developer makes a bad process, accidentally nukes 2.5 years of records

  11. newleafkratom on

    „…He also admitted he „over-relied on the AI agent to run Terraform commands“, and is now stopping the agent from doing so, and will manually review every plan Claude presents so he can run any destructive actions himself….“

  12. LongTrailEnjoyer on

    Working in IT and then development taught me to back my stuff up. I don’t feel bad for people like this.

  13. Should have said. never delete or overwrite backups… come on people… basic monkey’s paw rules.

  14. TomTomXD1234 on

    Going to be interesting to see the next generstion of programmers. I wonder if there will be a clear drop in quality of code being produced. We are seeing a slight drop already.

  15. The machine decided the project didn’t need to exist after writing 90% of the code.

  16. Wallie_Collie on

    I’ve gone hipshooter with claude a few times, I still guardrail my env and only allow claude a map read files for env variable names. Git executive permissions is also a risky move imo. Budgeting for DB backup is fundamental so I have no sympathy

  17. Slow_Watercress_4115 on

    nah, the headline should be „an inexperienced or mentally challenged developer gave access to production environment to an unpredictable AI tool“

  18. Oh man I’d love to see the fuckass comment from the AI after the handler told it about its mistake „Oh, sorry! I guess I did all that. Let me know if I can help you with anything else.“

  19. I just can’t let this thing run in auto mode. I check every shell command and approval them manually to make sure it’s not doing anything outside the current directory and not running any command that might have catastrophic affect on the project I am working on. These amateur vibe coders think just dictating it and letting it run in auto mode is all they have to do because the amateur influencers told them to do so.

  20. Lots of people just reading the headline here. Claude Code did nothing wrong in this situation, it’s 100% on the developer who pushed ahead with this despite repeated warnings. He specifically admitted on Twitter that „Claude was trying to talk me out of it, saying I should keep it separate“

    This whole thing is just extremely suspicious also, it wouldn’t surprise me if this was done on purpose specifically to get attention. He’s using it to promote his newsletter…

Leave A Reply