• Damir Zekić
  • April 2014

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.

Slide contents

  • I don't like Rails anymore
  • Ruby on Rails
  • Honeymoon
  • Example code
  • When is honeymoon over?
  • The Issues
  • The Issues
  • The Technical Issues
  • Solid
  • Solid (2)
  • Extra
  • Rails Application
  • The Technical Issues
  • When is Honemoon over?
  • Development Speed
  • Ruby on Rails
  • Development Speed
  • Ruby on Rails
  • /blank/
  • The Social Issues
  • How to Manage?
  • Alternatives to Rails
  • Alternatives to Rails (2)
  • Lotus
  • Lotus Components
  • Does Lotus Deliver?
  • Lotus tests
  • Lotus model tests
  • Lotus greenfield app
  • Recommended Materials
  • Questions?