When upgrading from Rails 3 to Rails 4, you need to add a couple of new settings; otherwise, JavaScript and CSS will no longer be minified in production.

Stafford Brooke writes about his first run in with turbolinks in Rails 4.

I posted a list of gems extracted from Rails 4. When upgrading a Rails 3 application, you may need to pull in a few of these.

I wrote about how easy it is to decode and view the contents of session cookies in Rails 3. A fully encrypted cookie store is coming in Rails 4.

I have released the first beta version of Upgrading to Rails 4. Rails 4 is not yet released, but might be soon. There are also certain features you can start using today in Rails 3.2 that have been extracted as gems.

I expect to release new content every 1-2 weeks as Rails 4 continues stabilizing.

I blog about some changes coming down the pipeline in capybara 2.0.

I've been using dumb_delegator for a while so I decided to release v0.5.0.

Introducing rake-rails: run ALL the things with `rake`, avoiding confusion with `rails`

Highgroove released the 1.0 version of git_tracker, making it easier to format commit messages that reference Pivotal Tracker stories.

More details in the README on GitHub.

Highgroove just released the zonebie gem: it runs your Rails/ActiveSupport tests in a random timezone to prevent bugs where code wrongly depends on a certain zone being set.

Over on the Highgroove blog, Brian posts some thoughts on writing readable ruby.

Over on the Highgroove blog, I posted about Rails and CanCan: Authorization for Specific Fields.

Just posted on the Highgroove blog about faking the filesystem in unit tests.

Be aware of database transactions when using callbacks to enqueue background jobs.

For those needing a really high level, quick start overview of testing authentication with RSpec request specs, I wrote up some examples.

Over on the Highgroove blog, I talk about optimistic locking with MongoDB and mongo_mapper.

Jonathan Wallace posts about one scenario when it makes sense to dip into SQL, even when using ActiveRecord.

Over on the Highgroove blog, I posted a small tip about using let and nested describe/context blocks with RSpec to DRY up test code.

Yesterday, I blogged about iterating through time with Rails; unfortunately at first I missed a terrible inefficiency in the code, which I explain in my next post, Beware of Ruby Sugar.

Cool tip I learned from @rjspotter: Iterating Through Time With Rails.

There are some potential gotchas when using instance_eval with a block to define methods (metaprogramming). I wrote a post exploring the details.

A closer look at blocks in Ruby and how they can sometimes produce unexpected results.