Why conventions matter in Ruby - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to print a greeting message using a conventional Ruby method.

Ruby

def greet
  puts [1]
end
greet

Drag options to blanks, or click blank then click option'

Aprint "Hello, world!"

B"Hello, world!"

Cecho "Hello, world!"

Dconsole.log("Hello, world!")

Attempts:

3 left

💡 Hint

Common Mistakes

Using print without quotes

Using JavaScript syntax like console.log

In Ruby, puts prints a string with a newline. The string must be in quotes.

2fill in blank

medium

Complete the code to define a class with a conventional Ruby naming style.

Ruby

class [1]
  def initialize(name)
    @name = name
  end
end

Drag options to blanks, or click blank then click option'

Aperson

BpersonClass

Cperson_class

DPerson

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase or snake_case for class names

Ruby classes use CamelCase starting with a capital letter by convention.

3fill in blank

hard

Fix the error in the method name to follow Ruby conventions.

Ruby

def [1](age)
  puts "Age is #{age}"
end

Drag options to blanks, or click blank then click option'

Aget_age

BGetAge

CgetAge

DGETAGE

Attempts:

3 left

💡 Hint

Common Mistakes

Using CamelCase or uppercase for method names

Ruby method names use snake_case with lowercase letters and underscores.

4fill in blank

hard

Fill both blanks to create a hash with symbol keys using Ruby conventions.

Ruby

person = { [1]: "Alice", [2]: 30 }

Drag options to blanks, or click blank then click option'

A:name

Bname

C:age

Dage

Attempts:

3 left

💡 Hint

Common Mistakes

Using strings or bare words as keys without colon

Ruby uses symbols (starting with :) as keys in hashes by convention.

5fill in blank

hard

Fill all three blanks to write a conventional Ruby loop that prints numbers 1 to 3.

Ruby

3.times do |[1]|
  puts [2] + [3]
end

Drag options to blanks, or click blank then click option'

Ai

C1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong variable names

Not adding 1 to start counting at 1

The block variable i counts from 0, so adding 1 prints numbers 1 to 3.

Practice

1. Why is it important to follow naming conventions like snake_case for methods and variables in Ruby?

easy

A. It automatically documents the code.

B. It makes the code easier to read and understand for everyone.

C. It prevents syntax errors.

D. It makes the program run faster.

Solution

1. Step 1: Understand the purpose of naming conventions

   Naming conventions like snake_case are designed to make code consistent and readable.

2. Step 2: Identify the benefit of readability

   Readable code helps both the original coder and others who read or maintain the code later.

3. Final Answer:

   It makes the code easier to read and understand for everyone. -> Option B

4. Quick Check:

   Readability = It makes the code easier to read and understand for everyone. [OK]

Hint: Think about what helps you read code easily [OK]

Common Mistakes:

• Confusing speed with readability
• Thinking conventions fix syntax errors
• Assuming conventions auto-document code

2. Which of the following is the correct way to name a Ruby class according to conventions?

easy

A. MyClass

B. my_class

C. myClass

D. MY_CLASS

Solution

1. Step 1: Recall Ruby class naming conventions

   Ruby classes use CamelCase starting with a capital letter.

2. Step 2: Match options to convention

   Only 'MyClass' follows CamelCase correctly.

3. Final Answer:

   MyClass -> Option A

4. Quick Check:

   Class names = CamelCase = MyClass [OK]

Hint: Classes use CapitalizedCamelCase, not snake_case [OK]

Common Mistakes:

• Using snake_case for classes
• Starting class names with lowercase letters
• Using all uppercase letters for classes

3. What will be the output of this Ruby code?

def my_method
  puts "Hello"
end

MyMethod()

medium

A. NoMethodError

B. SyntaxError

C. Hello

D. nil

Solution

1. Step 1: Check method definition and call

   The method is defined as 'my_method' (snake_case), but called as 'MyMethod' (CamelCase).

2. Step 2: Understand Ruby method name case sensitivity

   Ruby method names are case sensitive, so 'MyMethod' is not recognized.

3. Final Answer:

   NoMethodError -> Option A

4. Quick Check:

   Case sensitivity causes NoMethodError [OK]

Hint: Method names are case sensitive in Ruby [OK]

Common Mistakes:

• Ignoring case sensitivity in method calls
• Expecting automatic method name correction
• Confusing method names with class names

4. Identify the error in this Ruby code snippet:

class myclass
  def initialize
    @name = "Ruby"
  end
end

medium

A. Class keyword should be lowercase.

B. Instance variable @name is not allowed.

C. Missing parentheses in initialize method.

D. Class name should be in CamelCase, not lowercase.

Solution

1. Step 1: Check class naming convention

   Ruby classes must be named using CamelCase starting with a capital letter.

2. Step 2: Identify the incorrect class name

   'myclass' is all lowercase, which breaks convention and can cause confusion.

3. Final Answer:

   Class name should be in CamelCase, not lowercase. -> Option D

4. Quick Check:

   Class names = CamelCase = Class name should be in CamelCase, not lowercase. [OK]

Hint: Class names always start with a capital letter [OK]

Common Mistakes:

• Using lowercase for class names
• Thinking instance variables are invalid
• Believing parentheses are mandatory for initialize

5. You have a team project in Ruby. Why should you all agree to use snake_case for method names and CamelCase for classes consistently?

hard

A. To ensure the code runs faster on all machines.

B. To make the code look fancy and unique.

C. To improve collaboration by making code easy to read and maintain.

D. To avoid writing comments in the code.

Solution

1. Step 1: Understand team coding conventions

   Consistent naming helps everyone read and understand code quickly.

2. Step 2: Recognize collaboration benefits

   When all follow the same style, it reduces confusion and errors during teamwork.

3. Final Answer:

   To improve collaboration by making code easy to read and maintain. -> Option C

4. Quick Check:

   Collaboration needs consistency = To improve collaboration by making code easy to read and maintain. [OK]

Hint: Consistent style helps teams work smoothly together [OK]

Common Mistakes:

• Thinking conventions affect speed
• Believing style is for decoration only
• Assuming comments replace conventions