When we reach for it
Existing Ruby applications. Most of what we are asked to do here is get a long-running product safely onto supported versions and back under test.
A language optimised for developer expressiveness, and the foundation of a large population of production Rails applications that are still the right tool for their job.
Existing Ruby applications. Most of what we are asked to do here is get a long-running product safely onto supported versions and back under test.
We do not start new systems in Ruby. The reason is hiring and typing rather than the language itself, and we would rather be honest about that than pretend a technical case we do not hold.
Version upgrades, dependency untangling and characterisation tests around behaviour nobody wants to touch — the work that lets a team keep shipping in a codebase they had begun to describe as legacy.
Where this appears on the site
We work in Ruby, and no case study or service page currently published on this site prints it in its stack. Rather than describe an engagement you cannot check, this space stays empty until one does. Ask us and we will talk you through it directly.
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.