Wade Winningham in his article tries to answer "Questions Ruby on Rails skeptics ask"
If you decide to recommend using Rails with a team that doesn’t know much about it, you may run into some questions. If you don’t have some ready answers, the idea will most likely be shot down quickly and left in the dust.

The questions he tries to answer are:

  • Using ‘id’ as the primary key name ?

  • Using the Rails naming scheme ?

  • Rails generates too much database server traffic ?

  • It’s difficult to find hosting ?

  • What about performance ?


and if you have other questions, Wade say:
There’s a number of great places to find more information on how Rails works.
A number can be found on the Rails webpage for documentation. The Ruby on Rails API documentation is the most up-to-date resource since it is actually generated from the code itself although it’s more like looking up things in a dictionary.

It is a good article I have had a pleasure to read. I recommend it.