Insightful comment from the thread:
Yeah, I think part of the problem is that Facebook has never had an actual product which people pay for and expect to work. Their whole culture and set of priorities are counter to this.
Yeah, I think part of the problem is that Facebook has never had an actual product which people pay for and expect to work. Their whole culture and set of priorities are counter to this.
God help us all .
Same but with our Jenkins builds, which appear to be entirely non-deterministic. "Perhaps the praying will help," I think to myself as I create my PR.
I mean. It still is.
This is a reason why better education for all is the way forward for humanity.
People got so upset about the Catholic church selling the right to bend the divine rules that one guy wrote an extremely angry listicle, made a viral post on a church door, and the rest is history. And centuries of sectarian warfare.
(Seriously, most of the 95 theses are about indulgences: https://www.luther.de/en/95thesen.html )
Of course there is a discussion to have about incentivizing the _wrong_ behavior (the need to create publicity around issues that shouldn't exist in the first place / only people with "clout" become the ones who get their issues resolved).
[At a party] A: What do you do? B: I work for $BIGTECH. A: You suck dude. I bought one of their products and it never worked once.
People on HN are not really strangers, we are part of a community. By helping one of us, they help one of their in groups. Not helping might devalue their investment in this place.
HN users are the early adopters that small group of users who have much more influence early on in projects. Care of early adopters makes sense.
Bigger companies seem not to care that much, apart from maybe twitter? And those few thousand upvote posts on reddit.
They wouldn't allow just any employee to "fix" these issues. Too often there is a lot of context that is omitted from the shared story, so it's not just a matter of hitting a button to remove a block.
Also, "I helped a member of the public defeat my organisation's policy" is a negative on the resume not a positive. Sadly.
When the coin in the coffer rings / An account from bannination springs!
What about the 99.9% of the rest who don't have those contacts?
I cannot afford to ignore 0.01% of incoming requests because we charge per request. At a certain point, yes, money and pros and cons yadda yadda yadda. It just feels that, once again, people are saying, "but Google does it!" -- and that does not mean you should.
I'd say the biggest problem it the non-existent support. It's fine if 0.01% fails, as long as there is human troubleshooting or help available if necessary.
If 100% of users are experiencing 0.01% random errors it probably isn't worth bothering about.
If 0.01% of users are experiencing 100% errors than it is much more important.
[1] https://www.usenix.org/conference/nsdi20/presentation/hauer
Oh, please, you are confused. I worked at Google, most teams just don’t have metrics like this.
While I don’t think it’s acceptable, reality is that it’s expensive to compute such metric, i.e. you need to slice you monitoring stream per each user, has privacy implications, and often it’s unclear what action should be taken.