It is said that putting debug logs (console.log or printing stuff) is not considered a best debugging practice and people should learn various debug tools. For example, mastering DevTools.

But don't you think it might get a bit tricky for beginners?

I think beginners should definitely put console logs everywhere without "assuming something works certain way". You MAY THINK that the loop will always run but it just might not...?

Put logs everywhere to see what's going on.

Yes there are multitudes of debugging tools but console log is fast and clean.

𝐋𝐞𝐚𝐬𝐭 𝐓𝐫𝐚𝐧𝐬𝐩𝐚𝐫𝐞𝐧𝐜𝐲 = 𝐁𝐞𝐬𝐭 𝐃𝐞𝐛𝐮𝐠𝐠𝐢𝐧𝐠.

Well it's important to strike a balance. Here's a bit more detailed explanation with some coding examples:

function calculateSum(a, b) {
  console.log("Entering calculateSum"); // Debugging log
  if (typeof a !== 'number' || typeof b !== 'number') {
    console.error("Invalid input: Both 'a' and 'b' should be numbers.");
    return NaN;
  }
  const result = a + b;
  console.log(`Result of ${a} + ${b} is ${result}`); // Debugging log
  return result;
}

const num1 = 5;
const num2 = "10";

console.log(`The sum of ${num1} and ${num2} is ${calculateSum(num1, num2)}`); // Debugging log

Here are some points to consider:

1. Start with Console Logs: For beginners, using console logs is a great way to understand the flow and variables in your code. It can help you track the program's execution and identify issues.

2. Learn and Progress: While console logs are a helpful starting point, it's essential to continue learning and explore more advanced debugging tools like browser developer tools (DevTools) and IDE-specific debugging features.

3. Tailor Debugging Tools to the Task: Depending on the nature of the problem, certain debugging tools may be more effective. For complex issues, browser DevTools can provide a wealth of information.

4. Remove Logs Before Committing: It's crucial to remove debugging logs before sharing or committing your code. Failing to do so can clutter the codebase and make it difficult to maintain.

5. Use Conditionals: To avoid overloading your console with logs, consider using conditionals to enable or disable debugging logs. For example:
   

const DEBUG = true;

function someFunction() {
  if (DEBUG) {
    console.log("Debugging info");
  }
  // Rest of the function
}

// Toggle debugging logs
DEBUG = false;

In summary, console logs are a valuable tool, especially for beginners, to understand and troubleshoot code. However, it's essential to progress beyond this method and explore more sophisticated debugging tools as your skills grow. Balancing debugging techniques and keeping the codebase clean will ultimately lead to more efficient and maintainable software.

Happy Debugging! 🎉💻✨

Follow me for more such content:
LinkedIn: https://www.linkedin.com/in/shameeluddin/
Github: https://github.com/Shameel123