3 ms·
> Don't Do you mean "Don't give it more autonomy", or "Don't use it to access servers/dbs" ? I definitely want to be cautious, but I don't think I can go back
by nico 9mo ago
> Don't
Do you mean "Don't give it more autonomy", or "Don't use it to access servers/dbs" ?
I definitely want to be cautious, but I don't think I can go back to doing everything manually either
- JoshTriplett 9mo agoI mean, both, but in this case I'm saying "don't use it to access any kind of production resource", with a side order of "don't rely on simple sandboxing (e.g. command patterns) to prevent things like database deletions".
- dsr_ 9mo agoWhy aren't you using the tools we already have: ansible, salt, chef, puppet, bcfg2, cfengine... every one of which was designed to do systems administration at scale.
- dpoloncsak 9mo ago"Why would you use a new tool when other tools already exist?". Agents are here. Maybe a fad, maybe a mainstay. Doesn't hurt to play around with them and understand where you can (and can't) use them
- dsr_ 9mo agoPlay and production need to be separate domains. Otherwise, you don't have production, you only have play.
- dpoloncsak 9mo agoOkay...? Agreed. I still don't think the answer to "How are you guys giving LLMs access to your DBs?" is "Don't". Nowhere did OP or any of the comments in the chain specify they were testing Claude in production.
- bigstrat2003 9mo agoYou have to choose between laziness or having systems that the LLM can't screw up. You can't have both.
- hephaes7us 9mo agoYou can have it write code that you review (with whatever level of caution you wish) and then run that on real data/infrastructure. You get a lot of leverage that way, but it's still better than letting AI use your keys and act with full autonomy on stuff of consequence.