This is nothing new it's just faster. The very same lack of guardrails would allow a new, inexperienced employee, or a disgruntled employee, do the very same damage. AI just speed runs everything. If your AI can nuke prod accidentally, you failed to have the appropriate guardrails in place plain and simple. It is the same failure as before. Every time this happens, it is someone operating wildly out of their depth and why product people can't just vibe. Now more than ever, experienced engineers are essential.

[–] matlag@sh.itjust.works 6 points 20 hours ago (1 children)

Given corporates layoff engineers at dramatic rates, in a few years, we'll start to see services collapsing with no one left who can recover them.

[–] axus@lemmy.ca 2 points 18 hours ago (1 children)

And yet Twitter still exists

[–] atx_aquarian@lemmy.world 4 points 17 hours ago* (last edited 17 hours ago)

Twitter has to be the most basic problem, though. Shit loads of small data in, shit loads of small data out, basic search but no significant structure. Just index the shit out of it. Right? What am I missing? There's probably an AWS service that does it, just upload your theme CSS. (Last part was sarcasm.)

[–] llacook@lemmy.world 2 points 20 hours ago

This. There should have been processes in place to prevent this. But I can’t say I haven’t gone through it myself; not AI, but my own advanced imbecility.

[–] Napster153@lemmy.world 1 points 17 hours ago

They're about to run out of those experienced engineers in well under a decade as long as they keep strangling the entry level workforce.

Forcing seniors to work is also a recipe for disaster as well.