Category Ruby tips

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…

A security ticket lands in a Rails team’s queue: a customer can open another customer’s invoice by changing the number in a URL. The fix may involve only a few lines of Ruby. Finding the missing permission check, understanding the…

Enterprise applications typically generate large amounts of paperwork. When that paperwork comes as a PDF, someone must open the PDF, find the purchase order number, verify the amount and copy some details into another system. Nearby, a Rails application stores…

A scraper that worked on Friday and fails on Monday may have nothing wrong with its parser. The page might now be a login form, the proxy credentials could have expired, or the server could be asking the client to…

Build two small programs with one clear contract: Ruby exports a reading list and Swift decodes, validates and totals it.

Follow an order-summary program from data to output, then test empty input, incorrect types and missing keys.

Campaign spreadsheets get messy very fast. One person tracks followers, another tracks video views, and somebody else has the monthly service charge tucked away in a column. All of it relates to the same campaign, although the figures need different…

Choose a practical Ruby project by its inputs, output and failure rules, from a cleanup script to a shared web application.

GitHub, Shopify and Airbnb turn up in almost every list of websites made with Ruby. Familiar names are useful, but they only answer part of the question. How many sites use Ruby, and what does it mean when a crawler…

A Rails feature rarely stops with the Ruby code. A booking form needs a usable layout, a controller needs tests, and a slow dashboard may need its database queries reviewed. AI tools can help with these jobs, though each calls…