Filter

Sign up for our newsletter

Receive a selection of our favorite articles from our blog and around the web straight to your inbox.

Article  |  Development

Puma is the Preferred Web Server for Rails Developers

2 Jun 2016

Puma is the Preferred Web Server for Rails Developers

Puma’s popularity as both a web and Rails server has shown steady growth toward the position of preferred tool for both roles. Growing out of the once-mighty Mongrel, Puma hails itself as "A Modern, Concurrent Web Server for Ruby". Showing significantly lower memory usage and response times than Unicorn and Passenger the communities support appears to be continuing to shift in its direction.

Continue Reading

Article  |  Development

Still Not Tracking Exceptions in Rails

1 Jun 2016

Still Not Tracking Exceptions in Rails

A declining but still significant percentage of respondents to Planet Argon's Rails survey (down to 16% this year, from a high of 31% in 2009) don’t use any exception notification at all on their projects. Why turn a deaf ear to an important part of your application’s health?

Continue Reading

Article  |  Development

AngularJS vs Ember.js -- Comparing Apples to Oranges

27 Apr 2016

AngularJS vs Ember.js -- Comparing Apples to Oranges

We are awash in a sea of options for front-end Javascript frameworks. We all want the right tool for the right job, but separating useful information from noise can be tough & choosing the "correct" technology can be a daunting task. In an attempt to not add more fuel to the fire in the everlasting Ember vs. Angular debate, here is a list of some (relatively) unbiased comparisons between two of the most popular JS frameworks that we feel accurately summarize the pros & cons that come along with the tools being used to build modern web applications today.

Continue Reading

Article  |  Development

Debugging HTTP Requests with Sinatra

23 Feb 2016

Debugging HTTP Requests with Sinatra

Recently I was working on a task where I was attempting to connect to a third party API (from a Rails app using the HTTParty gem). The API had a fairly complicated authorization header that needed to be built, by concatenating the body of the request itself along with various authorization headers, then being hashed, and then being base64 encoded and escaped. If the header was improperly formed, all I saw was a 403 Forbidden response - not particularly helpful for debugging.

Continue Reading

Have a project that needs help?

New Call-to-action