[charcircuit]

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.

[b112]

It is absolutely necessary. Point in fact, most DEVs don't have access to PROD either. Specialists do.

Clause, maybe, is a junior DEV.

Not a release engineer.

[abustamam]

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.

[charcircuit]

>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.

[abustamam]

> 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.

[charcircuit]

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.

[abustamam]

There were backups. The AI deleted them.

[charcircuit]

When people talk about backups they typically mean located somewhere else. If one terraform command can take out the db and the backups then those backups aren't really separate. It's like using RAID as a backup. Sure it may help, but there are cases where you can lose everything.

[QuercusMax]

Nobody, not even a "smart robot" should have unfettered read-write production access without guardrails. Read-only? Sure - that's a totally different story.

Read-write production access without even the equivalent of "sudo" is just insane and asking for trouble.

[esseph]

> Keeping a human in the loop is not necessary.

You don't work in anything considered Safety Critical, do you?