A customer asks about a charter flight for Friday. Later, they change the departure airport, add another passenger and ask whether the original quote still applies. The team now has several emails describing different versions of the same trip. That…
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…
Every small agency has some version of the same problem: the client says they sent the file, the project manager remembers seeing it, and nobody can find the approved copy. A client document portal makes a useful Ruby on Rails…
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 job looks simple on a calendar. There is a date, a customer and something that needs doing. Open the email thread behind the job, though, and things become more complicated. For instance, someone wants to move the appointment. A…
Saving a link takes a moment. Recalling why you saved it can take considerably longer. You see a headline, so you keep the tab open. A few days later, dozens of tabs are in front of you and the detail…
A Ruby script that fetches one price is easy enough to leave in a single file. Add account balances, signed requests and a feed that stays open all afternoon, and that file starts getting awkward. The HTTP code needs one…
The order says paid, and the payment provider shows a completed transaction. Yet the bank deposit is smaller than the invoice. Someone has to explain the difference. This gives you a starting point for a Ruby on Rails project: a…
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.