Sidekiq good practices

It seems that writing Sidekiq’s workers it’s quite an effortless task. Still, during my eight-year journey with this great library, I experienced too many issues caused by poorly designed background jobs to believe that it’s an easy thing to do.For sure, a badly designed background job can lead to the following issues:Exhausting the API calls limit due to performing the same call too many timesSending the same e-mail to the same recipient multiple timesCreating classes that are hard to test and debugand probably many more. This article is my list of good practices that help me write better classes and design more reliable systems that heavily depend on the background job processing.