Convention over configuration principle in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the 'Convention over Configuration' principle mean in Rails?

It means Rails uses standard defaults so developers don't have to write extra setup code. If you follow Rails' naming and structure rules, things just work.

beginner

How does 'Convention over Configuration' help speed up development?

By using common defaults, Rails reduces the need to write repetitive setup code. Developers focus on unique parts of their app instead of configuring every detail.

beginner

Give an example of a Rails convention that follows this principle.

If you create a model named 'Article', Rails expects the database table to be named 'articles'. You don’t have to tell Rails the table name explicitly.

intermediate

What happens if you don’t follow Rails conventions?

You must write extra configuration code to tell Rails how to find files, tables, or routes. This can slow development and add complexity.

beginner

Why is 'Convention over Configuration' good for beginners?

It helps beginners by reducing choices and setup. They can learn Rails by following simple rules and see results faster without getting stuck on setup details.

What does 'Convention over Configuration' encourage in Rails?

A Avoiding any configuration or conventions

B Writing detailed configuration files for everything

C Ignoring Rails defaults and customizing all settings

D Using standard defaults to reduce setup

Rails uses standard defaults so developers write less setup code.

If your model is named 'User', what table name does Rails expect by default?

A users

B user

C User

D user_table

Rails pluralizes model names to find the corresponding database table.

What must you do if you don’t follow Rails conventions?

A Write extra configuration to tell Rails your setup

B Restart the server multiple times

C Nothing, Rails automatically adjusts

D Use a different framework

Without conventions, you must configure Rails manually.

Which of these is a benefit of 'Convention over Configuration'?

A More errors

B More setup time

C Faster development

D Less code reuse

Following conventions speeds up development by reducing setup.

How does 'Convention over Configuration' help beginners?

A By forcing them to write complex configs

B By reducing setup choices and simplifying learning

C By hiding all code details

D By requiring advanced knowledge

It simplifies learning by using standard rules and defaults.

Explain the 'Convention over Configuration' principle in Rails and why it matters.

Think about how Rails expects files and names to be organized.

Describe what happens if you do not follow Rails conventions and how it affects your project.

Consider the extra work required when Rails defaults don’t match your setup.