DRY (Don't Repeat Yourself) in Software Engineering - Time & Space Complexity
Analyzing time complexity helps us see how following the DRY principle affects the speed of our code.
We want to know how avoiding repeated code impacts the number of steps the program takes.
Analyze the time complexity of the following code snippet.
function calculateSum(arr) {
let sum = 0;
for (let i = 0; i < arr.length; i++) {
sum += arr[i];
}
return sum;
}
function calculateAverage(arr) {
let total = calculateSum(arr);
return total / arr.length;
}
This code calculates the sum of numbers in an array and then uses that to find the average, reusing the sum calculation instead of repeating the loop.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: A single loop that goes through the array once to sum all elements.
- How many times: The loop runs exactly once per function call to
calculateSum.
As the array size grows, the number of steps grows in a straight line with it.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | 10 steps to sum |
| 100 | 100 steps to sum |
| 1000 | 1000 steps to sum |
Pattern observation: The work grows evenly as the input grows; doubling input doubles the work.
Time Complexity: O(n)
This means the time to run grows directly with the size of the input array.
[X] Wrong: "Calling the sum function twice is just as fast as calling it once."
[OK] Correct: Each call loops through the array, so calling it twice doubles the work and time.
Understanding how reusing code affects time helps you write cleaner and faster programs, a skill valued in real projects and interviews.
"What if the sum calculation was repeated inside the average function instead of calling a separate function? How would the time complexity change?"