What's also bad about this incident is that it was hidden from the public during a weekend because they were having a Moto GP that weekend and didn't want the publicity.
This is a great article, it got me thinking on better uses of the iPad and the whole setup on a virtual machine using terraform, docker, etc is also a good way of thinking on how to work remotely. Thank you for sharing.
I love this post, I was at Gophercon and met several gophers. This post shows how the Go community is made and how we're going forward. Thank you @codegangasta.
Not really, Zendesk has being there since Aug 2011 and the block between 6th and 5th is way better. I walk this block everyday and it changed, for good.
Well, in Brazil 10 percent is already included in the check, it's "optional" but everybody accepts it. Usually that's not related to good or bad service, it's the common practice. And this money doesn't go to the server but to the 'proprietor'.
I'd say go before it's too late. Being there, done that. After 3 years I realized that the founders wouldn't change their M.O. And that was after writing 3 products, developing the team, deploying the thing. There are plenty of good start-ups to work. Take that lesson as lesson learned and move on.
As I see they are not taking care of their customers. If just have a retention policy of the data after the cancelation, let's say for 3 days, or a week, the problem could have being avoided. Win-win situation.
Rewriting the front-end using Javascript and Backbone won't fix the backend problems necessarily. How about reducing the objects creation and tuning the backend too?