Using Ruby to parse CSVs can be extremely helpful. With a few tweaks and know-how, anyone can process and evaluate data efficiently and accurately.
Active Record shares all the benefits and drawbacks of ORMs in general. You'll have a much easier time using it if you avoid making these 4 small mistakes.
I love Rails, but the recommended way to work with callbacks is a set of terrible practices for building a real app.
Extending Ruby's built-in classes is convenient but dangerous. Use refinements to get fine grained control over your monkey patches.
Phoenix framework is a functional solution for traditional model-template-view applications. It can replace Ruby on Rails—but at a cost.
How to set up the Ember front end to request data from the Rails back end that we got up and running in my previous post.
How to set up a Rails AIP to share data between an Ember.js web frontend and a Rails backend.
N+1 queries are quick to sneak in and can wreak havoc on performance. This approach will help you find them quickly, write the test, and preload correctly.
Using code generation for your Rails utility scripts (like importing demo data into production) that can then be executed remotely (no need to deploy).
What if we used Active Record to build the query we want for the count of each child record, then used a named scope to nicely place that as a sub-select?
One-liners can be piped into the heroku run console command—what about longer scripts you write locally and want to execute in a remote Heroku environment?
Active Record is a powerful tool, but there are occasions where letting the database handle work for us is the correct answer.