The right tools for the job - efficient web application development | NetEngine

The right tools for the job - efficient web application development

Blog
Ricardo Friday, 7 December 2012

We’re very glad to admit that here at NetEngine we’ve got clients that allow us to use what we consider the most appropriate tools for their projects.

It’s not big news that for each brand new project we need to follow different requirements. That said, we have found a few common third party tools that we’ve been using heavily across all projects to help us on development, improving, monitoring and communicating with our clients.

  1. Bugsnag

    Despite knowing it is crucial not to have bugs in production, sometimes it happens. We always keep an eye on it and Bugsnag helps us to trace a bug down. It is an excellent tool if you want to be notified straight away and control what is resolved or not.

    Bugsnag

  2. Papertrail

    In addition to Bugsnag helping to debug whether an exception raises, we also use Papertrail. This is an awesome tool to keep our logs centralized and search for events and errors from a simple interface. Its search is fast and gives you the option of parsing the log based on time. In short – you don’t need to ssh into your server and grep your logs.

    Papertrailapp

  3. Newrelic

    Newrelic defines itself as “a developer’s best friend” and definitily is a must-have. We’ve been constantly chasing out perfomance improvements, removing bottlenecks and monitoring all our clients applications ever since with NewRelic. We wrote a blog post about a huge performance improvement in one of the projects we’ve developed. Check it out here

    Newrelic

  4. Sprintly

    We want to show to our clients what we’ve been working on and keep them informed about the progress of a new feature or a bugfix. Sprintly simply works. Its interface has heaps of cool features such as real-time notifications, easy priority changes and full of filters. The highlights of Sprintly goes to GitHub’s integration. We just need to refer the task number in the commit message and it is automatically added as a new comment and linked to a Github commit page. Besides that, it has a simple natural language parsing, which means that if you say as your commit message “Fixes #42”, the item #42 will move into the ‘Done’ column. Our clients are very happy to use it and that’s what we want.

    Sprintly

Of course we are not stuck with these amazing tools and we always want to try new ones, but these four above have impressed us and are helping a lot.

We want to hear from you now, what are your favourite tools?

comments powered by Disqus