Background jobs are used a lot in production. At first, the concept may seem complex or unclear why we are using it. So without a lengthy introduction let’s jump into action with a simple example.
Did you get
RuntimeError: can't add a new key into hash during iteration error?
I saw a lot of projects where the default date format was used. In fact, customizing the date format to provide a human-readable date will be very welcomed from your customers!
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: