Sometimes I’m consulted with refactoring a legacy RoR application that I’ve never seen before. That’s when an informed use of certain code metrics can come in very handy:
Quite often, legacy Ruby on Rails applications come with a fairly large amount of unused code. While it may be tempting to think about this as ballast to be deleted, that is rarely advisable. Most of the time, abandoned code tells something about the path of history a project took, so it’s a primary location to look at, evaluate and decide what and how to transform, rebuild or delete.