> Ruby on Rails follows the paradigm of Convention Over Configuration, that means that, if we name things in specific ways, and put things in specific places, t

> Ruby on Rails follows the paradigm of Convention Over Configuration, that means that, if we name things in specific ways, and put things in specific places, the framework will do its “magic” and we’ll have all the good benefits. > This is really powerful, it enables us to write less code and get a lot of functionality for free. It’s one of the reasons why Rails makes building new apps so easy. > But again, there’s a catch here and we have to be careful, conventions are great but we can get unexpected behaviors if we don’t know them. Indeed, at this point the framework is tantamount to a language unto itself. See also PHP vs. WordPress. Further still, we get into IDEs that take over the situation, e.g. Eclipse vs. IntelliJ. Not only do we have to fret the Java distribution, but have to deal with the tooling for editing/building the code. Nor does the problem seem to improve over time, except through one's retirement.