Enterprise rails written by Dan Chak is good. I have worked in Amazon.
His point of view is unique, but his arguments are well-founded.
For more information, see Amazon's book reviews. The method recommended by Dan Chak is anti-rails.
For example, he is not familiar with MySQL. "If you want to use a database, use PostgreSQL, PostgreSQL DDL, and migration script written in Ruby"
I have not fully accepted some of his ideas, but it is worth noting.
For example, he strongly suggested transferring the decoractor code to the plugin module to make full use of Ruby's management mechanism. He opposed using git's submodule mechanism instead.
I understand this. For details about the troubles caused by Git-submodule, refer to here (GIT submodule tells me that sub-module version A is available, but this version is not a formal release version, because there is no such force mechanism, the fact is that a does not exist or is accidentally deleted by someone, so I am miserable.) The solution can be analogous to Ruby (now the language is elisp ), use the Emacs package management mechanism elpa instead of Git-submodule.