Yet this seems to have been quite effective, given that the head of Developer Relations at Twitter is replying to this story on HN..
Yet this seems to have been quite effective, given that the head of Developer Relations at Twitter is replying to this story on HN..
Public shaming on twitter+blog is 50/50. It often gets the attention of an engineer and sometimes even a founder, and when it does the response is often reasonable. Why would you ever try anything else?
I've had a crazy technical issue with AWS that our account representative proved useless for about but a tweet got it fixed. Also see news articles about people suffering the most ridiculous treatment from comcast/timewarner/verizon/at&t until they get in the news and everything is finally sorted out. This is a totally standard thing you should already be familiar with. The problem is that these big companies get too many queries from crazies and people who have no idea what they're doing, they're inundated with stupid support requests. So a legitimate support request will never be noticed by anyone who knows anything. So you need a sort of public vetting process. You need the "shaming" part to express the priority in large companies where business people have all the power.
I'm not sure there's a better way, that's just how it is.
Going public means getting in front of people that care more about customers or has more time to do so. It feels a little like skipping the line though.