News for hackers. Stuff that matters.
Re:What we learned in 6 months of working on an AI Developer by c0balt on Sunday March 03, 2024 @07:04PM (#39585711)
> That should be quite easy

SysAdmin stuff is quite easy in terms of complexity to some sw stuff. The problems, similar to traditional engineering, tend to come from the rather high cost of failure.

To expand further, it's easy to setup a system but hard to setup one that's reliable and/ or resilient. It's hard to maintain systems that are not documented and/ or wrongly documented (outdated, inaccurate). It's even harder to always make sure everything's consistent and you don't lose/ damage data.

Re:What we learned in 6 months of working on an AI Developer by jaggederest on Sunday March 03, 2024 @07:28PM (#39585840)
Yeah imagine giving an AI root access to the server with your production database on it. Now I really want to try that in a VM to see what will happen. Even odds at some point it tries to rm-rf everything.
Re:What we learned in 6 months of working on an AI Developer by samus on Monday March 04, 2024 @01:09AM (#39587476)
Nobody is considering giving AI unrestricted access to anything yet. Code written by AI is reviewed by humans, and I would be shocked to hear that sysadmins are considering letting AI agents execute arbitrary commands.
Re:What we learned in 6 months of working on an AI Developer by singularity2001 on Monday March 04, 2024 @03:15AM (#39588157)
I gave GPT root access, so far without regrets

admittedly I recently added a soft barrier "for dangerous commands please ask for confirmation"

Re:What we learned in 6 months of working on an AI Developer by samus on Monday March 04, 2024 @03:37AM (#39588266)
Username checks out!
Re:What we learned in 6 months of working on an AI Developer by ofrzeta on Monday March 04, 2024 @05:20AM (#39588819)
Does it "know" what's "dangerous"?