Our company is framed around the following core beliefs:

1. Always try to use the right tool for the right job
2. Ruby provides our team greater productivity and effectiveness
3. You don't have to be a genius to get the same productivity out of Ruby

We are going to walk through a the details of a real engagement we have with a large enterprise, building core features in Ruby and Rails. We'll examine the difference between the Ruby development process and their prior experience building the same features in Java, and we'll talk about the experience of bringing their internal development team up to speed with Ruby and Rails.

Along the way, we'll look at how we managed the codebase and the standard churn of an enterprise product and their effects on the codebase. We'll see rUnit and Selenium acceptance testing, and take a hard look at the project statistics and what they tell us about the suitability of Ruby and Rails in an enterprise setting.