About Rails Rehab
Most software delivery problems aren’t caused by a lack of engineering talent. They’re caused by successful systems growing beyond the structure that originally made them successful.
A Rails application built around five engineers can struggle under twenty. Architecture that once accelerated delivery can begin slowing it down. Team practices that made sense during one stage of growth become sources of friction in the next.
Over time, the application becomes harder to change.
Features take longer. Deployments require more coordination. Engineers become too cautious around parts of the system that nobody fully understands.
The common response is to look for a technical solution: refactoring projects, rewrites, new tooling, additional process, or additional engineers.
Sometimes those things help. Often they don’t.
That’s because the visible symptoms aren’t always where the real constraint exists.
Rails Rehab was created to help growing Rails teams identify the real causes that are slowing delivery and address them with the smallest effective intervention.
Why a systems approach matters
Most consulting engagements start by examining the codebase. Code matters but software delivery is much more than the codebase alone.
Applications are shaped by the teams that maintain them, the decisions that created them, and the business pressures that influence them.
Two systems with identical technical problems can require completely different solutions depending on how they are used and operated.
That’s why Rails Rehab approaches delivery problems as systems problems.
Team coordination, ownership boundaries, operational habits, and business priorities all influence which technical interventions will actually improve delivery.
Looking at the whole system makes it possible to identify which constraint is actually limiting delivery, rather than treating whichever symptom happens to be most visible.
That broader perspective often reveals that surprisingly small changes can produce disproportionate improvements.
About Dave
Rails Rehab is a new consultancy led by Dave Kinkead, a software architect and engineer with more than 25 years of experience across software systems, military operations, commercial leadership, and academic philosophy.
He has worked across large-scale software systems and organisational environments where the constraints were no longer purely technical but structural — how teams coordinate, how decisions propagate, and how delivery systems behave under load.
Before founding Rails Rehab, Dave led operational teams and commercial business units across multiple countries, managed multi-million-dollar P&Ls, and served as a Maritime Warfare Officer in the Royal Australian Navy — environments where decision-making under uncertainty, system reliability, and operational accountability were non-negotiable.
That combination matters for one reason — it makes the problem visible at the system level.
Performance problems rarely originate where they first appear.
Most technical consulting treats delivery problems as code problems, process problems, or team problems in isolation.
By looking beyond the codebase to the wider delivery system, Rails Rehab helps teams identify the changes that will have the greatest impact with the least disruption.
When software slows down, it is rarely because teams stopped knowing how to build. It is because the system they are building within no longer reflects the system they are trying to run.
Rails Rehab exists to close that gap.