What is the point in logging a for loop to the console and could you complete the challenge without doing so?

JavaScript
1

Continuing the discussion from freeCodeCamp Challenge Guide: Nesting For Loops:

Context
Nesting For Loops
If you have a multi-dimensional array, you can use the same logic as the prior waypoint to loop through both the array and any sub-arrays. Here is an example:

var arr = [
  [1,2], [3,4], [5,6]
];
for (var i=0; i < arr.length; i++) {
  for (var j=0; j < arr[i].length; j++) {
    console.log(arr[i][j]);
  }
}

This outputs each sub-element in arr one at a time. Note that for the inner loop, we are checking the .length of arr[i], since arr[i] is itself an array.

Instructions
Modify function multiplyAll so that it multiplies the product variable by each number in the sub-arrays of arr


function multiplyAll(arr) {
  var product = 1;
  // Only change code below this line
  for (var i=0; i < arr.length; i++) {
  for (var j=0; j < arr[i].length; j++) {
    console.log(arr[i][j]);
    product*=arr[i][j];
  }
}

  // Only change code above this line
  return product;
}

// Modify values below to test your code
multiplyAll([[1,2],[3,4],[5,6,7]]);
2

The console is a very important tool in development and debugging. Developers use console.log() statements to track the state of their code throughout execution. It’s a tool for verifying that the state of your algorithm is what you expect it to be at any given time and to tell at what point things go sideways. During the development process, especially as projects become more complex, console logging is a common way to “sanity check” what you have so far so that you know you are moving forward on a solid foundation.

2 Likes