I'm excited to announce that I am a co-author of The Rails 4 Way. I'm joined with Obie Fernandez himself, and fellow co-authors Vitaly Kushner and Ari Lerner.

A lot of Ruby developers are familiar with queues, such as DelayedJob and Resque. While these queues have been predominant the last couple of years, my tool of choice is Sidekiq, a Redis backed queue by Mike Perham. Sidekiq advertises that a single process can do the work of 20 Resque or DelayedJob processes. Another benefit of Sidekiq is the inclusion of extensions, which allows for testing and delayed mailers.

In yesterday's post Retina Web Design, we covered multiple techniques to be "retina-ready" for the upcoming wave of double density screens. One of the techniques mentioned was to use retina.js, a JavaScript library that attempts to serve higher resolution images for visitors of your web application. To ensure even your uploaded image assets will work with retina.js, we can utilize CarrierWave to upload both standard and high resolution image versions.

Devices with retina displays are changing the way we design web applications. When Apple introduced the iPhone 4, we got a glimpse into how images on our sites look on retina enabled screens. Last year, the retina enabled iPad and Macbook Pro came to market, highlighting the fact that most web sites are not retina-ready.

If you're a Rails developer, you're familiar with with the standard way of sharing data from the controller layer to the view layer. By convention, Rails copies all instance variables defined in the execution of a controller action to the view context. This standard usage will result in strong coupling between your controllers and views, as they are sharing state via instance variables. To solve this problem, Stephen Caudill created the decent_exposure gem ...