evgeniydemin

I’m working on a Rails upgrade for a giant monolith application. It’s been a while already, and while I’m encountering many issues trying to jump from 5.2+ right to 6.1, I want to share some of the stories.

Are you a user of FactoryBot?

If so, I highly recommend taking a look at the FactoryTrace gem!

This gem is designed to automatically detect and identify unused factories and traits in your codebase. It's a fantastic tool for keeping your code clean and removing any unnecessary clutter.

I recently stumbled upon a perplexing discrepancy while converting Time to DateTime using the #to_datetime method. Intrigued by this unexpected behavior, I delved into an investigation to unravel its root cause. I’ll share my findings in this blog post with you, as I believe it’s worth your attention.

Writing CRUD controllers in Rails may seem easy, but as your application grows, you'll find it increasingly difficult to maintain and update your code. In this article, you'll learn why extracting business logic from your controllers and creating focused, testable business actions is a necessary change.

These simple facts can help boost your application's performance or avoid memory bloats.

Thank you very much for your comments! I appreciate that!

So far, I see that N+1 is a "measurable" problem that doesn't have to be removed with an additional layer of hidden complexity.

I'm sorry; I didn't know memes are considered bad things. I'm experimenting with "facing" pictures and haven't found my style so far.

What kind of image would you suggest I have on posts like this?

Why would you spend your time dealing with annoying N+1 problems when you can enable auto-preloading and forget about it for good? Are you surprised it's possible? Check it out!

It’s a popular internet recommendation to use eager loading in Ruby on Rails applications to eliminate the N+1 query problem. It may seem like a blessing initially, but it has drawbacks. Gladly, there is a much better solution I want to share with you.

Glad that you liked it! True about timecop.

Are you interested in how Ruby stores numbers in memory? It can look not very sensible initially, but knowing this can help you grow professionally.

Unfortunately, I learned it the hard way. Check out the article to avoid the same mistakes.