alt Hacker Newsthey're doing as well as professionals do without oversight on production environments. There's no lack of stories about people deleting their production environments with data loss too.
the fix has always been to limit what can be done directly to prod, and put it through both review, and tests before a change can touch production.
Replies
> they're doing as well as professionals do without oversight on production environments.
That's nonsense. First, most people haven't deleted the production environment by accident. They have enough sense to recognize that as a dangerous thing and will pause to think about it. Second, the ones who do make that mistake learn and won't make it again, which is not something the clanker is capable of.
So you're saying they need oversight... from a professional. Preferably someone with years of experience and domain expertise, who knows how to not fuck everything up?
> they're doing as well as professionals do without oversight on production environments
The difference is that if a human does it there usually is done accountability, you’ll be asked how it happened and expected to learn from it. And if you do it again your social score goes down, nobody will trust you and you’ll be consider a liability. If a cli tool does it the outcome is different, you might stop saying the tool or you might blame yourself for not giving the tool enough context. And if it does it again you might just shrug it off with “well of course, it’s just a tool”.