The next simplecov version will include a new coverage mode - github.com/simplecov-ruby/si….
If you use code coverage on CI, you might see a big performance boost, as we had. Our CI runtime dropped from 15 minutes to 10 with this simple change 😱.
Got the first million downloads for one of my gems! 🎉
It was my first gem, and it became the most used.
If you use CircleCI, make sure to use blobless checkout.
It reduced our checkout step from 1 minute to 20 seconds!🚀And it is used in quite a lot of places.
Created a new gem to lazily load specified Active Record columns - github.com/fatkodima/activer…
This can greatly reduce IO 📉 and improve queries (and application's) performance 📈if you have some large db columns that are not used most of the time.
We had the same problem, so I created a new gem that allows to add deadlines to ignored columns, and this won't happen again - github.com/fatkodima/smart_i…
Dima Fatko 🇺🇦 retweeted
The next Rails version will have an optimization to enqueue many emails at once github.com/rails/rails/pull/… (if the active job adapter supports bulk enqueuing, like sidekiq).
Very useful for batch operations and can greatly reduce the number of round-trips to the queue datastore.
The next Rails version will have an optimization to enqueue many emails at once github.com/rails/rails/pull/… (if the active job adapter supports bulk enqueuing, like sidekiq).
Very useful for batch operations and can greatly reduce the number of round-trips to the queue datastore.
Just yesterday it helped me again to identify exact places of performance problems in a long running job 🫰.
APM and other tools were useless. Found exact places of N+1s, lines that load too many records, most popular SQL queries, redundant queries, etc.
Highly recommend!
Presenting a new gem for tracing Active Record, I wish existed earlier 😆 github.com/fatkodima/active_…
Many times I crafted code to get similar reports like in the gem - to profile slow tests, rake tasks, jobs, find the most popular queries etc.
I hope you will find it useful too.
5
645
Very happy about this change to rubocop github.com/rubocop/rubocop/p…
Very often I see people use the `&.` operator without giving much thought. That change does a deeper analysis of the code and will help to reduce unneeded `&.`, making code nicer. I found 250 such cases in my app.
A nice optimization was merged, which makes Rails batching over whole (or almost whole) tables even faster. 🎉
github.com/rails/rails/pull/…
This is probably more costly than changing programming languages, because of existing users, but are there examples where people migrated from GraphQL back to REST API? Or wish to do the migration?
What is your experience with GraphQL so far as an implementer and/or a user?
3
2
813
It is scary when idiots like musk have so much power and influence. In ideal world, such people must be isolated from society.
Or, more likely, he writes such statements purposefully.
Sorry, I hate tweeting about politics, but having this idiot on our planet is too much.
15
1,319
Does anyone use bg data migrations from my online_migrations gem? Do you find it useful, useless for your use case? Please respond here or in github issues or DM.
After testing on a large project, I realised there are some significant flaws in it and going to reimplement it. /1
Instead of one style of writing blocks, there are now 2.
While reading the code, instead of descriptive names, you now need to remember what this meaningless 'it' refers to each time.
While this might work for trivial cases, it will be abused for chained calls and be a hell.
13
45
6,742
The future Rails 8.1 will help solve a popular problem many teams have - constant merge conflicts in the structure.sql file at the head of the versions list.
You need to provide a custom formatter. If sorting by, e.g., hashes of versions, the conflicts now will be very rare.
Link to the PR github.com/rails/rails/pull/…
1
518