A Ruby application can work well for years before one job starts taking too long. A nightly import may spend hours parsing files. A calculation may hold up requests even though the rest of the Rails application has little to…
A Ruby developer’s guide to Instagram Highlights: the history of old gems, current API limits, manual download options and authorised Story archiving.
A Rails test works for your colleague but fails on your laptop. Before changing the application, check Ruby versions, installed gems and database configurations. A difference in the setup can send you looking for a bug that has little to…
A wardrobe tracker makes a useful Ruby project because its rules are easy to inspect. An item belongs to someone, has a category and may be available to wear. An outfit combines several items. A wear log records what actually…
The Rails application boots on its new cloud host. The home page loads, staff can sign in, and the migration looks finished. Then someone downloads an old attachment and gets an error. A scheduled export runs twice. The database reaches…
Let’s say you’ve got an inbox for support inside your Rails app. A customer has sent 6 messages. Two people have responded. Now someone else opens up that ticket and wants to know what happened. A little bit of context…
A Ruby web crawler may start out with three proxy servers and a call to Array#sample. That can work at first. Later, a proxy begins to fail, retries repeat more work than expected, and the database fills with pages that…
Picture a familiar Rails support problem: a customer has requested a CSV export, the application has accepted it, and the download never arrives. You open the dashboard. Everything looks fine. Somewhere behind that working interface, an export job is waiting…
A referral has been sent, but nobody knows whether the specialist got it. Reception checks the electronic health record (EHR). A nurse searches her inbox. Another employee looks at the spreadsheet. Consider a Ruby on Rails project built around that…
In many cases, all we want to view in a Ruby demo is one simple thing, like finding out which button caused a Rails form to fail. Instead, our demo is two minutes long. And the file size is equal…