Hacker News new | past | comments | ask | show | jobs | submit login

I'm sorry, but "PR crisis" continues the worrying (if thankfully rare) trend of people talking about this whole ... situation like it's an unfortunate but incidental bug that just needs to be ironed over, akin to some kind of "cost of doing business". There is a very important category difference between, say, Cloudbleed, and allegations of sexual harassment.

Bounds-checking errors and the like do happen, and in rare cases reach catastrophic proportions, as we saw today. Downplaying what happened in that kind of situation isn't quite right, but it's still victimless in a certain sense -- you're minimizing the PR damage to yourself while not exactly hurting any other party. But Uber's behaviour here is essentially an attempt to apply the kind of "mitigation" that a situation report for a security vulnerability documents to a human conflict. (Non-serious aside: do they have an in-house "Fowler incident report" being edited every ten minutes?) It'd be far more admirable if they could go the completely Homo economicus route and declare "We don't honestly care, as long as we're profitable, and we're going to do everything possible to combat this eventuality." or something along those lines that actually reflects what they think of this, but obviously that would be ... suboptimal.

Yes, Uber management may be (in fact, from the emails they're sending out to people "deleting Uber", they definitely are) suffering as a result, but the lack of a contrite "Yes, this happened, it shouldn't have" instead of the "This is contrary to our values, our ethos, and a few other words that conjure associations of fine, upstanding citizenship in our communities and such" (read "Lies!"), together with the obviously impartial steps they're taking to "investigate" the matter, make it difficult to find empathy for their pain here.

(Any strawmen or logically suspect arguments in the above are unintentional and I'd love being told about them. Damn, I'd use that for an HN signature if those were supported.)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: