We're helping product teams focus on building great software by building automated crash monitoring for web and mobile apps. Half of a typical developer’s time is currently spent finding and fixing bugs; we aim to bring that number as close to zero as possible, by automating the entire error monitoring process.
We already work with some of the world's fastest growing and most innovative companies like Square, GitHub, Mashable, Goodreads, Buffer, Heroku (and thousands more). We’re currently doubling revenue every 3 months and we're now expanding our team of 6.
You could trivially restructure the code to factor out global page actions into an object, like this:
// Make a global page actions object
PageActions = {
selectAll: function (event, context) {...},
nextPage: function (event, context) {...},
prevPage: function (event, context) {...},
};
// Hook up clicks to global actions
// Eg: <a href="#" data-action="selectAll">All</a>
$("[data-action]").click(function () {
var action = $(this).data("action");
PageActions.selectAll("click", this);
});
// Hook up keypresses to global actions
Mousetrap.bind("a", function () {
PageActions.selectAll("keypress", this);
});
This would help with code structure and organization, at the cost of flexibility.
This is actually a really good point, I've seen many sites take the approach of adding keyboard shortcuts but avoiding the main "default" actions, (eg. space bar, up, down).
James from Bugsnag here, we're constantly rolling out tons of new features to speed up the find/fix/deploy bug hunting cycle. I'm surprised so many people are still using emails for error monitoring, using a hosted service like Bugsnag/airbrake/rollbar will massively help with productivity and actionability.
We've been using Inc in beta at Bugsnag for the last couple of weeks, super useful product. HipChat integration is the best feature. Integrating with existing workflows a far better solution to inbox overload.
The number of pull requests I get where the diffs are completely unreadable because someone has this feature enabled is insane. On certain whitespace dependent languages (I'm looking at you Python) simply supressing the whitespace in the diff is not an option.
What are the arguments for having whitespace removal as a coding standard?
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 :)
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.
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.
Have you spent any time working out the total market size for your app? Doing some basic modeling might help you make your decision!