Rails

🚨 The Problem Everything worked fine locally—but CI kept failing. I was working on a Rails application that used two databases: A primary database (fully controlled by the app) A secondary database (owned by a different application) Here’s the catch: 👉 The secondary database was read-only from my app’s perspective. Locally, this wasn’t an issue because the database already existed and had the expected schema. But in CI: The secondary database didn’t exist Rails tried to interact with it like a normal DB Tests failed with missing tables and connection errors 🔍 Root Cause The issue came down to this: ...

🚨 The Problem I was working on a Rails app that integrated with Slack for two main features: Mapping Slack users to our HR app Sending notifications to Slack users or channels Everything worked fine locally, but in staging and production, Slack rate-limit errors (429 Too Many Requests) started appearing: Mapping users required fetching the Slack user list repeatedly Sending notifications in bulk triggered multiple API requests in a short time Some requests failed, causing unreliable notifications and mapping 🔍 Root Cause Slack imposes strict rate limits per API method. ...