You might be interested in Agile Development with Rails by Sam Ruby, Dave Thomas.
You could skip the "Building Application" part and go straight to Rails in Depth part.
I quote the introduction to this last part:
For the rest of the book, we’ll go through Rails topic by topic (which pretty much means module by module). You have seen most of these modules in action before. We will cover not only what each module does but also how to extend or even replace the module and why you might want to do so. The chapters in Part III cover all the major subsystems of Rails: Active Record, Active Resource, Action Pack (including both Action Controller and Action View), and Active Support. This is followed by an in-depth look at migrations. Then we are going to delve into the interior of Rails and show how the com- ponents are put together, how they start up, and how they can be replaced. Having shown how the parts of Rails can be put together, we’ll complete this book with a survey of a number of popular replacement parts, many of which can be used outside of Rails. But first, we need to set the scene. This chapter covers all the high-level stuff you need to know to understand the rest: directory structures, configuration, and environments.
I don't know if I have right to paste this but if that can make you buy this book, I'm sure the author would agree!
To become good at Rails in my opinion you should first be sure that you understand Ruby well. I would suggest browsing through (careful reading is not necessary if you're already an established programmer) some of the basic ruby books like: Why's Poignant Guide to Ruby and Programming Ruby.
After this, you should become familiar with the Rails API's and DSL's, I would suggest beginning with reading Ruby on Rails Guides. When you understand the Rails basics the ultimate Rails reference is Ryan Bates' excellent Railscasts. If you don't like watching videos the site has an ascii mirror. Even if you don't have a specific task in mind, go watch a few of these to really understand the way problems are tackled in Rails.
Ofcourse when it comes to actually gaining skill in developing Rails skills, it is imperative that you try your hand at actually making a few Rails applications. Rails has a notoriously steep learning curve, so it's best when you have tried a few simple unimportant applications before you try to build your life's work with Rails.
发布评论
评论（2）
您可能对 Sam Ruby、Dave Thomas 所著的使用 Rails 进行敏捷开发感兴趣。
您可以跳过“构建应用程序”部分，直接进入深入了解 Rails 部分。
我引用最后一部分的介绍：
我不知道我是否有权粘贴此内容，但如果这能让您购买这本书，我相信作者会同意的！
You might be interested in Agile Development with Rails by Sam Ruby, Dave Thomas.
You could skip the "Building Application" part and go straight to Rails in Depth part.
I quote the introduction to this last part:
I don't know if I have right to paste this but if that can make you buy this book, I'm sure the author would agree!
在我看来，要擅长 Rails，您首先应该确保自己很好地理解 Ruby。我建议浏览一些基本的 Ruby 书籍（如果您已经是一名成熟的程序员，则无需仔细阅读），例如： 为什么是 Ruby 的精彩指南
和编程 Ruby。
之后，您应该熟悉 Rails API 和 DSL，我建议您首先阅读 Ruby on Rails 指南。当您了解 Rails 基础知识时，Rails 的终极参考是 Ryan Bates 的优秀 Railscasts。如果您不喜欢观看视频，该网站有一个 ascii 镜像。即使您心中没有特定的任务，也可以观看其中的一些内容，以真正了解 Rails 中解决问题的方式。
当然，当要真正获得开发 Rails 技能时，您必须亲自尝试实际制作一些 Rails 应用程序。 Rails 的学习曲线非常陡峭，因此在尝试使用 Rails 构建您一生的工作之前，最好先尝试一些简单的、不重要的应用程序。
To become good at Rails in my opinion you should first be sure that you understand Ruby well. I would suggest browsing through (careful reading is not necessary if you're already an established programmer) some of the basic ruby books like: Why's Poignant Guide to Ruby
and Programming Ruby.
After this, you should become familiar with the Rails API's and DSL's, I would suggest beginning with reading Ruby on Rails Guides. When you understand the Rails basics the ultimate Rails reference is Ryan Bates' excellent Railscasts. If you don't like watching videos the site has an ascii mirror. Even if you don't have a specific task in mind, go watch a few of these to really understand the way problems are tackled in Rails.
Ofcourse when it comes to actually gaining skill in developing Rails skills, it is imperative that you try your hand at actually making a few Rails applications. Rails has a notoriously steep learning curve, so it's best when you have tried a few simple unimportant applications before you try to build your life's work with Rails.