Currently the best method I’ve got is too use Newrelic’s RPM service.

According to DHH a Rails application does not need too much documentation. (check the post here)

This refresh button will update only the table itself via an Ajax call.

Testing controllers let me understand what are mocks and stubs.

Testing has_many, and habtm relationships with RSpec is now DRY.

The first, and the “good enough” reason to test your Ruby on Rails application thoroughly is that Ruby is not a compiler but an interpreter, if not tested your application can halt even on a banal syntax error.

Users will be able to customize columns like in this example (click the “Customize” button)

By using the magic render_component.

Sometimes a model managed with ActiveScaffold must be visualized/configured in different ways.

Subforms are handling weird hidden/excluded AS fields.