Education Ruby / Rails despite the articles on Habré

I am writing to my personal blog so be careful. “Construction work is under way,” “wear a helmet,” “there have already been accidents” and all that ...



2009 started with a large number of educational articles on Habré. Drops, ounces, buckets and cups pour into us from all sides. I am confused by the contents of these containers. More specifically, let's talk about learning the Ruby language and the Rails framework.
')
I am sure that training in our craft is necessary. It is necessary. Therefore, in principle, what the guys decided to do is wonderful. However, this is in theory. In practice, training is a responsible occupation. This is so if only because retraining in case of improper learning is much more difficult than learning for the first time.

So what are we being taught and what are we not being taught in the RoR article ?

• We are with you, habrachitel, say about ActiveRecord and models but do not say anything about REST and resources.
• You and I are not told anything about migration with the help of which models are created and changed.
• When we talk about ActionView, we hear about layouts and templates, but not about partials, the use of which is practically mandatory for any project and the non-use of which can turn any project into impassable jungle.
• In a conversation about controllers, we already do not hear about the resources.
• We can guess about automated testing from the media description in the application. And we can not guess, because This article is intended for Rails newbies.
• Roads? What are such routes? Are they important?
• Nothing is said about rail plug-ins, how to use them and where to find them.

Do I want to say that the article is useless? In no case. The postscript talks about caution with literature. For the sake of this article could be published. But why then such a long 'entry'? For the three lines of text?

And it doesn’t surprise me at all that the very first commentator speaks about the similarity of RoR with Symfony. Such an opinion can be formed because the description of Rails is not so wrong. Rather, this description does not reflect the fundamentals and fundamental concepts used in Rails. Therefore, Rails after such a description may resemble something else. Just like you can take a vague silhouette of a man in the fog for your friend Vasya. When the fog clears, it will immediately become clear that this is not a man, but a woman. Not white, but Chinese. One-legged. :)

After reading all this, the hacker may ask: "What do you suggest people who want to learn Ruby and Rails to do?" “Rails Way” by Obi Fernandez. These three books need to be read exactly in the order in which I listed them to you. This will give you really deep knowledge of both the language and the framework.