Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lawrencewalters/8c6a9df75855a49f1d8e to your computer and use it in GitHub Desktop.
Save lawrencewalters/8c6a9df75855a49f1d8e to your computer and use it in GitHub Desktop.
Basic Ruby on rails - The Rails Philosophy

Explain how "convention over configuration" allows us to be more productive as a group.

Convention over configuration gets all the basics out of the way. All the tiny decisions like "how should I organize my project file structure" that could involve a lot of thinking (how do I future proof this?) are already made - by convention. We learn the same, single convention, and then we all follow it. This means when we switch projects, or start new, we don't spend a lot of time figuring out basic context - we can get right to the heart of the functionality we are working with. Another higher level example is akin to the shopping cart platform. Assume we are building a transactional ecommerce website. If we start with an off the shelf product that has a home page, PDP, cart, checkout - the basic stuff is already done for us. There's no reason for us to rethink this very straightforward thing that thousands of people have already built. This lets us move right to the interesting parts - customizing it for our business. In this example, the cart is the "convention".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment