Hacker Newsnew | past | comments | ask | show | jobs | submit | more foobar2k's commentslogin

Congrats to the Exceptional team!

For anyone looking to switch from Airbrake/Exceptional to a more modern/reliable error tracking product, check out our product Bugsnag (https://bugsnag.com).


James from Bugsnag here. We make sure to reply to people asap, we've set up Help Scout (https://www.helpscout.net) to manage the replies to these emails, so even if I'm out of the office, my co-founder can jump on and reply.

Our target is to reply within 10 minutes, unless we are asleep :)


James, you're doing much better than me! I've been slipping on my reply times recently to up to 2 days which totally sucks.

One thing I started doing is taking an hour of zero-distraction time every morning to fire off responses to emails that come in to support.

Unfortunately we don't have anyone handling customer responses full time, but we're getting to where we should. Responses to emails are a blessing and a curse, but I wouldn't trade em for the world.


Chris from Vero here. This is the method we use. Essentially, setup a group mailbox that everyone can respond to.

I use chrish@getvero.com instead of chris@getvero.com to send the emails. 'chrish' goes to the entire team.

I remember seeing HelloFax do this way back in May 2012 (at least, as far as I can remember!) and it was very effective.


Ian from Segment.io here and +1, we've also just started using HelpScout to handle having lots of messages going to all four of us. It was the nicest solution we found for keeping the personal touch still, since they don't add weird support crap to your emails.

Also the graphs for response time as fun to monitor. Accidentally let one request go over night the other day and really messed up my average ;p


Thanks for mentioning Helpscout! Amazing product.


For those asking "why is HipChat better than X", one of the big reasons lies with the number of integrations with other products.

Our product Bugsnag (https://bugsnag.com) has HipChat integration, so you can instantly see errors from your apps appear in your chat room. We've also set up curl scripts to post into chat whenever there is a deploy, or push to GitHub.


I completely agree with this. We (bugsnag) are running on rails 4 beta right now to help iron out any production issues before that is released.

We didn't, however, realize that "patch" releases also have release candidates. I'd recommend following the rails blog (http://weblog.rubyonrails.org/) which announces release candidate builds too.


Thanks for the blog post - and I didn't realize that patch releases also had RC.

It looks like this release was quite fat, for a patch release.

I added "check rails diff" to my deploy todo list.

EDIT: I just noticed that http://weblog.rubyonrails.org/ doesn't have a way to subscribe by email. I signed-up by email with this site instead http://blogtrottr.com, in case it helps other here.


You can also subscribe to the rails-core mailing list, all betas, RC and full releases get announced there.


There's quite a bit more discussions on rails-core apart from RC and releases, so subscribing to the blog is a good idea if your time is limited :-)


Please stop feeding this obvious troll


I completely agree, huge barrier to entry.


The bigger financial barrier to entry is buying a Mac and iPhone (for those who don't own these).

After that, $99 is not a big sacrifice and you quickly recuperate your money even if you sell your app for 99¢.

I am both an iOS and Mac developer ($99 x 2 per year) and I'm in the black and then some with a couple of apps sold between 99¢ and $2.99.


Complete agree, also the idea of self hosting content in order to save a few $ is really not something we can ever expect - nor should we ask for it IMO.

One of the best features of the app store is that from the consumers perspective its smooth, reliable and just works. Having lots of "cheap" app developers trying to save $100 / yr by hosting their app bin's themselves could results in an unreliable market place that ultimately drives people away from it.


Actually I think that's exactly the point... it somewhat limits the amount of crappy apps that could get to the approval stage.


Huge congrats to the Crittercism team. My company Bugsnag (https://bugsnag.com) also provides error monitoring for mobile apps, but it is interesting to see Crittercism's shift in focus towards performance monitoring.


There's no such thing as a quick DNS change.


My startup NameTerrific can support instantaneous DNS updates in a geo-redundant Anycast infrastructure. As long as your TTL is sufficiently low (<300), the impact is quite limited as propagation time is negligible at NameTerrific.

EDIT: Sorry guys. We got some issues with a gem after installing the recently updated ruby2.0.0p0. The unicorn workers were timing out. TerrificDNS is completely unaffected and the site is already running again.


https://www.nameterrific.com/pricing

"We're sorry, but something went wrong."


Not the best advertising

http://www.nameterrific.com

"502 Bad Gateway

nginx/1.2.7"


Hopefully the back-end is not running Ruby. ;-)


The back-end is AWS Route53, it seems.


Well, we have already soft launched our own TerrificDNS Anycast and it has replaced the Route 53 solution. TerrificDNS platform is running on Redis + PowerDNS.


Terrific.


It's up now. Please see parent for explanation. Sorry!


From my experience with DNS for a large site over the last years, a lot of ISPs do not respect your TTL and have their own TTL (often 24h).


If and only if the site's end users and their software fully respects TTL. A lot don't, especially shitty mobile networks and web browsers.


You should probably put the same amount of effort into your web hosting infrastructure http://imgur.com/ok5lfml


Nameterrific is down. https://www.nameterrific.com/


Python has ConfigParser which parses ini-style config files, I assume it uses some standard grammar.

http://docs.python.org/2/library/configparser.html


Seems to use a different approach to Stripe, using encryption rather than API hooks/callbacks.


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

Search: