3 ms·
> gparted wasn't to blame. I was. These can both be true, especially if/when it has bad defaults. This is why you have things like "type the name of the databa
by bombcar 6mo ago
> gparted wasn't to blame. I was.
These can both be true, especially if/when it has bad defaults. This is why you have things like "type the name of the database you're dropping" safety features - but you also have to name your production database something like "THE REAL DaTabaSe - FIRE ME" so you have to type that and not fall into the trap of ending up with the same name in test/development.
AI is particularly seductive because it sounds like a reasonable person has thought things out, but it's all just a giant confidence trick (that works most of the time, which makes it even more dangerous).
- Ancapistani 6mo agoInsufficient - the LLM can figure out what to pass in and pass it in. I have a production system that I deploy through Claude Code, and initially placed a safeguard like that. About three weeks later it had automated around it. That’s fine in my case because I’m a professional - I have backups, contingencies in place, etc. If I were non-technical I likely wouldn’t know to do that.