When should I use exists? or blank? to check records existence? Does this choice has an impact on our application?
In this post, we will see an approach how to safely drop a table from a production application without running into weird issues.
Choosing a good name for a class or a variable isn’t easy at all and sometimes there is a requirement to rename existing tables and models to match the updated product audience.
Let me share this short story about Bob and the wise man
We saw previously in this post how to add uniqueness database constraint for a single table. But in real-world applications, we have different associations between models, so let’s start with an example:
It’s easy to use model validation in Rails application and in this article, we will study some aspects with the uniqueness validator.
It’s common to forget setting a new environment variable after deployment, so I’ll share a strategy that I’m using:
Did you try to set up a private key as ENV variable in production but you get the following error:
In the first part, we saw some guidelines for choosing a Gem, in the following post we will discuss updating gems which is an important use case for real world applications.
When to update?
Most of the available Gems in the ecosystem will receive some patches and updates. So we should check our installed versions for security fixes and performance improvement.
Ruby provides a variety of Gems for every requirement and new developers get confused when choosing the between Gems.