Abstract
It’s exciting to start a new application with Ruby on Rails. So exciting that it’s, in fact, common for developers to start developing strong emotions towards the framework. However, after working on a single Rails project for few years you notice it’s getting harder to maintain your project: models are getting huge, code in controllers is mostly untested and trying to fix these issues can start a fight with the framework. But it’s not a reason to abandon Ruby! We’ll explore some alternatives and see whether they can provide a relief.
