As our asynchronous tasks consumption grew, our DevOps team started noticing sudden memory spikes and attributed it to the Sidekiq processes. Apparently, after the background task has finished processing the memory held by the process,it is not released back to the system

Do you want to become a Ruby committer? Are you interested in learning from language designers? Do you want to get in the loop on conversations in the Ruby open-sourced development community? If so, this post is for you

Consider the costs: the email threads, the 1:1s, the small meetings, the large meetings, the meeting prep, the mockups and samples prepared, the time spent communicating the decision, the meetings to rehash the decision and the opportunity costs of all that time/energy that could be spent elsewhere