Why conventions matter in Ruby - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of method naming convention in Ruby

What will be the output of this Ruby code that follows the naming convention for predicate methods?

Ruby

def valid?
  true
end

puts valid?

A nil

B false

C SyntaxError

D true

💡 Hint

Predicate methods in Ruby usually end with a question mark and return true or false.

In Ruby, methods ending with '?' are used to indicate they return a boolean value. Here, valid? returns true, so puts valid? prints true.

🧠 Conceptual

intermediate

Why follow Ruby conventions for variable names?

Why is it important to follow Ruby conventions for variable names, such as using snake_case?

A It prevents syntax errors in Ruby.

B It ensures code readability and consistency across Ruby projects.

C It makes the code run faster.

D It automatically documents the code.

💡 Hint

Think about how other programmers read your code.

Using snake_case for variables is a Ruby convention that helps everyone read and understand the code easily, making collaboration smoother.

🔧 Debug

advanced

Identify the error caused by ignoring Ruby method naming conventions

What error will this Ruby code produce and why?

Ruby

def CalculateSum(a, b)
  a + b
end

puts CalculateSum(3, 4)

A No error; outputs 7

B NameError because method names should be snake_case

C SyntaxError due to capital letters in method name

D ArgumentError because of wrong method definition

💡 Hint

Ruby allows method names with capital letters but it is not a convention.

Ruby allows method names with capital letters, so this code runs and outputs 7. However, it breaks the convention of using snake_case, which can confuse readers.

❓ Predict Output

advanced

Effect of ignoring Ruby constant naming conventions

What will be the output of this Ruby code that ignores constant naming conventions?

Ruby

Pi = 3.14
puts Pi
Pi = 3.14159
puts Pi

A SyntaxError due to reassignment of constant

B 3.14\n3.14159

C Runtime warning and outputs 3.14\n3.14159

D 3.14\n3.14

💡 Hint

Ruby allows reassignment of constants but warns you.

Ruby lets you reassign constants but gives a warning. The code outputs both values, showing the reassignment worked but is discouraged.

🧠 Conceptual

expert

Why do Ruby developers prefer convention over configuration?

Why is the principle of 'convention over configuration' important in Ruby development?

A It reduces the number of decisions developers must make, speeding up development.

B It forces developers to write more configuration files.

C It makes Ruby code run faster by optimizing configurations.

D It allows developers to ignore best practices.

💡 Hint

Think about how conventions help avoid repetitive setup.

Ruby's 'convention over configuration' means developers follow standard ways to do things, so they spend less time setting up and more time building features.