Just like omakase sushi is solely the chef's choice, the biggest benefit to any framework is when it makes (good) decisions for you.
I've learned a few things the hard way. How to properly use Active Record callbacks with Ruby on Rails is one of those things.
How to use a "www" subdomain as your primary domain on a Rails app hosted with Heroku.
Turbolinks is a great idea in theory, but it comes with enough problems to offset its benefits.
Sometimes you need to get to a class that you have deleted or renamed within a migration file. Here's how you do it.
You got yourself into that pickle where you created a migration, migrated, deleted the migration, then tried to rollback. Here's how you get around it!
You can avoid multiple requests to your server by rendering SVG images inline to the rest of your HTML.
Post a message to one of your Slack channels when your Rails app encounters a 500 error.
That whole killing two birds with one stone approach might just work in using PaperTrail as an activity log, at least in simpler projects.
Transitioning from one database to another, or even to a whole new database with a new adapter, can be tough. Here's an easy way to transition content.