Over the past year at Gusto, we’ve drastically changed how we approach Sidekiq in our main Rails monolith. Our changes have reduced costs, reduced the number of outages, made it simpler for product engineers to use Sidekiq, and improved the customer experience.
At some point in growing a large-scale software system, you’ll require “out of band” context: data which is not explicitly passed as an argument to a function but rather implicitly attached to the request, job or event being processed.
Upgrading Rails can often be difficult and risky! I'll be walking through the process my team took to safely upgrade to Rails 7.0. While this is going to be relatively Rails and Ruby specific, I hope you can take away something for software you are upgrading.
Governing the delivery effectively and improving engineering productivity plays a vital role in setting teams up for success. Read on to learn more about Thoughtworks' framework for engineering productivity governance.
In performance work, I often find that work in the "middle" of the effort distribution lacks the effort-to-benefit ratio of the "low" and "high" effort ends.
RuboCop’s motto has always been “The Ruby Linter that Serves and Protects”. Now, with the addition of a server mode in RuboCop 1.31 that motto is truer than ever!