Description:

At TaxiMagic we've been working on the same rails application for 3 years. As such we've tried nearly everything rails has to offer. I'll go over what has worked for us and what hasn't, and additionally I'll slide in some "to do's", including using ruby's flexibility to easily build "driver" classes, when single table inheritance works and when it doesn't, using acts_as_state_machine, when not to be DRY, using look up models and associated caching, understanding database issues (null/not null, indexes, unique, indexes, limit, etc.), using named scopes, employing queuing/backgrounding/croning, and using web services/APIs.