Why conventions matter in Ruby - Performance Analysis

Time Complexity: Why conventions matter in Ruby

O(n)

Understanding Time Complexity

When we write Ruby code, following conventions helps keep things clear and consistent.

We want to see how using or ignoring conventions affects how long code takes to run.

Scenario Under Consideration

Analyze the time complexity of the following Ruby method that sums numbers in an array.

def sum_numbers(numbers)
  total = 0
  numbers.each do |num|
    total += num
  end
  total
end

This method adds up all numbers in the list one by one.

Identify Repeating Operations

Look for loops or repeated steps.

• Primary operation: Adding each number to total inside the loop.
• How many times: Once for every number in the list.

How Execution Grows With Input

As the list gets bigger, the method does more additions.

Input Size (n)	Approx. Operations
10	10 additions
100	100 additions
1000	1000 additions

Pattern observation: The work grows directly with the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time to finish grows in a straight line as the list gets bigger.

Common Mistake

[X] Wrong: "Using different variable names or styles changes how fast the code runs."

[OK] Correct: Variable names or style do not affect how many steps the computer takes, only how easy it is for people to read and maintain the code.

Interview Connect

Understanding how conventions affect code clarity and performance helps you write better Ruby code that others can easily understand and maintain.

Self-Check

"What if we changed the method to sum only even numbers? How would the time complexity change?"