- cross-posted to:
- sysadmin@reddthat.com
- cross-posted to:
- sysadmin@reddthat.com
though the company insists the downtime was ultimately due to human error.
I suppose using
hat on top of a hat technology“agentic” “AI” in the first place is technically a human error.The error was executive management pushing this AI at all costs narrative.
The blame being placed on a low ranking human.
Their reasoning that it’s a human error is, because the user gave the AI too much permissions. So does this mean this is ultimately the fault of the ceo? Because a manager gave some employee the permission to do such a thing. And another manager that manager, etc… So by this reasoning everything is always the ceo’s fault. Let’s fire him!
Vibed too close to the sun.
Best headline 2026 so far lmfao
They just need to vibe harder.
Luckily, that’s exactly their plan.
Evidence that vibe coding makes even AWS go to shit.
And of course their answer is to plan to vibe coder better, in the future. 🤖💩
To be fair, if I was tasked with improving Cost Explorer my first step would also be to delete the existing product
Skill issues
Because of course the skillful choice is to avoid the dumpster fire of slop code at all costs




