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

We should all spend a moment to really take in the fact that Yelp is a website that has reviews of restaraunts and other services. That this person needed to be on call 24/7 for a review website.

Not a hospital. Nothing was burning down. Not even transportation or infrastructure related.

A review website. 24/7/365. For a review website.




It’s a big site, so any downtime is a lot of lost revenue. I’m sure the cost of 24/7/365 coverage is justified.

The trouble is that they apparently don’t want to pay for actual 24/7 coverage with a defined on-call schedule. They just try to declare it into existence.


I think you're sending this same message, but just to rephrase it - 24/7 coverage is important to the business due to the continuous traffic they receive, but 24/7 coverage has to be provided by multiple people and/or teams; it shouldn't and can't be an individual responsibility.


That is indeed what I was implying, but it’s good to state it explicitly.




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

Search: