Why change-impact analysis is surprisingly hard in Ruby on Rails

Refactoring a mature Rails app often starts with a simple question: If I change this method, what else could break? In a smaller codebase, grep might be enough. In a larger Rails app, not really. A method can be connected through: callbacks associations routes background jobs mailers concerns templates tests indirect Ruby callers And because Ruby...