It's been completely reliable when there were actual problems. The web interface was pretty intuitive to us as well. I really like the login flow.
Our PagerDuty is integrated right now with Scout, Pingdom, and our own custom alerting system.
So far most complaints we've had while using the service for the first week were our own faults: for example, our monitoring was too sensitive, which was fixed by using the regexp filters, and by eliminating spurious errors from reporting on our side. One thing that PagerDuty did was that it basically forced us to fix these reporting issues so that we weren't woken up at 5AM unless it was a real emergency.
The SMS interface got a little confusing when we had two errors at once. For example, a frequent case is getting two pages at once, "Service X is DOWN" and "quora.com is DOWN". I think what I tried doing was:
1. Receive the first report (site).
2. Receive the second report (service).
3. ACK both reports using the second report's code.
4. Fix the service.
5. Attempt to resolve the second report, receive a "code already used" error.
Resolving things via SMS is a little bit clumsy (it's what I usually default to). A link to the PagerDuty login would be cool, but I don't know if it would fit in the 160 character limit.
Thanks for the feedback! Very good point, we should allow you to send multiple replies per SMS alert to ack and then resolve (currently, there's a limit of one reply per alert).
You need your existing (real) password to change your password; e-mail is still possible to change. Probable attack vector is to do "lost password" link and then change it, but the same is applicable to anyone with a smartphone too (it just now applies to anyone with any phone hooked up to FB).
For the most part, schema changes can be done without breaking the existing code base (add columns, add tables, etc.) These schema changes can just be run on the databases before the code depending on it is pushed. Much more rarely though, there might be code that depends on a certain schema (the kind that say, alter table might do). In this case we can push out code that is compatible with both versions (at the very worst case, using table descriptions to differentiate between the two), run the schema change, and then eliminate the backwards compatibility.
There's not that much different in terms of operating procedure between continuous code deployment and scheduled code deployments; it's just much faster and less prone to merge errors.
The Russians were barely able to slow down Facebook back in 2009. Unless someone on 4chan has a bigger botnet and just decided for lulz to DDoS Facebook, 4chan would not even come close to generating enough traffic to register on the #2 website on the Internet.
'Disingenuous' isn't quite the word I would use. I'm sure the author really does think he's contributing to The Crusade, which is precisely the problem. He can't just dissect the errors in Arrington's logic. No, that's not good enough.
He needs to put on a Crusader uniform and act like he thinks those people are supposed to act: offended. He can't just BE offended, he must explicitly tell you he's offended, and start swinging his sword around so you know what a noble Crusader he is.
If he were responding to a blog post offensive to men, would he have used that language? No, because being offended for yourself isn't noble, it's being offended for others. And telling everyone about it as much as you can. How else will people know what an altruist you are?
Come now, we can be more mature than this. The OP may be an oversimplification of the issue, but that doesn't mean that he doesn't earnestly see and want to fix a problem.
One thing is that it took a long, long time for women to break into medicine and start being taken seriously as doctors. Tech is still relatively young, so I'm hoping that we can start making movements towards that level of parity faster than then several generations it took medicine.
Sure, if you count from the beginning of the medical profession (though technically, women dominated some parts of medicine, like delivering babies, for millennia before men ever became involved, and then women broke back in).
If you count from the beginning of women-in-the-workplace style feminism, software should have had women almost from the outset. If a new profession or a new sector of the economy arose now you'd expect it to have tons of women because as a culture we're used to women in the workplace, right? What about biotech--are there more women in biotech than software?
Our PagerDuty is integrated right now with Scout, Pingdom, and our own custom alerting system.
So far most complaints we've had while using the service for the first week were our own faults: for example, our monitoring was too sensitive, which was fixed by using the regexp filters, and by eliminating spurious errors from reporting on our side. One thing that PagerDuty did was that it basically forced us to fix these reporting issues so that we weren't woken up at 5AM unless it was a real emergency.
The SMS interface got a little confusing when we had two errors at once. For example, a frequent case is getting two pages at once, "Service X is DOWN" and "quora.com is DOWN". I think what I tried doing was:
1. Receive the first report (site).
2. Receive the second report (service).
3. ACK both reports using the second report's code.
4. Fix the service.
5. Attempt to resolve the second report, receive a "code already used" error.
Resolving things via SMS is a little bit clumsy (it's what I usually default to). A link to the PagerDuty login would be cool, but I don't know if it would fit in the 160 character limit.