Hacker News Reader

Comment by binsquare | Hacker News Reader

The internal disruption reviews are going to be fun :)

The fun is really gonna start if the root cause of this somehow implicates an AI as a primary cause.

It's never an AI's fault since it's up to a human to implement the AI and put in a process that prevents this stuff from happening.

So blame humans even if an AI wrote some bad code.

I agree but then again it’s always a humans fault in the end. So probably a root cause will have a bit more neuance. I was more thinking of the possible headlines and how that would potentially affect the public AI debate. Since this event is big enough to actually get the attention of eg risk management at not-insignificant orgs.

> but then again it’s always a humans fault in the end

Disagree, a human might be the cause/trigger, but the fault is pretty much always systemic. A whole lot of things has to happen for that last person to cause the problem.

Also agree. “What” build the system though? (Humans)

Edit: and more important who governed the system, ie made decisions about maintainance, staffing, training, processes and so on

I haven't seen the "90% of our code is AI" nonsense from Amazon.

Their business doesn't depend on selling AI so they have the luxury of not needing to be in on that grift.

https://archive.is/b6aUD

It’s gonna be DNS

Your remark made me laugh, but..:

"Oct 20 3:35 AM PDT The underlying DNS issue has been fully mitigated, and most AWS Service operations are succeeding normally now. Some requests may be throttled while we work toward full resolution."

https://health.aws.amazon.com/health/status

It’s always DNS! Except when it’s the firewall.

if that's the case it'll be buried

Reply on news.ycombinator.com