News for hackers. Stuff that matters.
Re:Claude Code 2.0 by saberience on Tuesday September 30, 2025 @08:24AM (#45424575)
But this is just like giving a junior engineer access to a prod K8s cluster and having them work for hours on stuff related to said cluster... you wouldn't do it. Or at least, I wouldn't do it.

In my own career, when I was a junior, I fucked up a prod database... which is why we generally don't give junior/associate people to much access to critical infra. Junior Engineers aren't "dangerous" but we just don't give them too much access/authority too soon.

Claude Code is actually way smarter than a junior engineer in my experience, but I wouldn't give it direct access to a prod database or servers, it's not needed.

Re:Claude Code 2.0 by simonw on Tuesday September 30, 2025 @09:30AM (#45425198)
You and I are advocating for the same exact solution here! Don't give your LLM over-privileged access to production systems.

My way of explaining that to people is to say that it's dangerous to do things like that.

Re:Claude Code 2.0 by hiatus on Tuesday September 30, 2025 @10:28AM (#45425916)
> Junior Engineers aren't "dangerous" but we just don't give them too much access/authority too soon.

If it is not dangerous to give them this access, why not grant it?

Re:Claude Code 2.0 by brulard on Tuesday September 30, 2025 @12:52PM (#45427941)
what value would that provide? If we give claude code access, even though very risky, it can provide value, but what upside is to letting junior to production?