Live data from Hacker News

High-Tech Solution to Disaster Response May Be Too Good to Be True

nytimes.com

1–10 of 23 posts

Re: High-Tech Solution to Disaster Response May Be Too Good to Be True

#3
For one, it’s great to see startups tackling hard problems like this: generally I believe there is huge benefit and opportunity for startups in providing government services like this. It certainly helps to dispel the feeling that our brightest minds are working on ads.

Secondly, this really seems like the initial phases of product development and fit — agencies would be foolish to simply rely on a startup like this to coordinate 100% of disaster response, I’m sure FEMA has similar models. With startups, especially ones tackling more “serious” domains (for lack of a better word) I’m willing to have a longer leash and proceed with caution.

Re: High-Tech Solution to Disaster Response May Be Too Good to Be True

#6

“We really think we can enable a disaster-free future.” That statement gave me pause since it's quite the unrealistic claim to make.

maybe a disaster is a poorly managed incident. You perhaps cant stop incidents but can stop poor management of them

Re: High-Tech Solution to Disaster Response May Be Too Good to Be True

#9

Wow. "AI" and emergencies are such a bad fit. ML is great at probably being almost right. That's not how you want to run critical systems.

Turns out, humans are also pretty good at probably being almost right. Luckily though, they've figured out how to build systems with higher fault tolerance than their own.

Re: High-Tech Solution to Disaster Response May Be Too Good to Be True

#10

Wow. "AI" and emergencies are such a bad fit. ML is great at probably being almost right. That's not how you want to run critical systems.

Turns out, humans are also pretty good at probably being almost right. Luckily though, they've figured out how to build systems with higher fault tolerance than their own.

It's easy for an ML model to do great in the average case but horribly in the worst case, so you're correct if "fault tolerance" is a simple loss function to be minimized, but wrong if "fault tolerance" actually means what we care about. That's much harder and not something we uniformly know how to do with ML. Like the costco example in the article.

To do that with ML, they'd need a loss function that captures what we care about and data it sounds like they don't have.

We do know how to build systems with high fault tolerance the old fashioned non "AI" way.

Post reply on HN