Course contentsShow
← JavaScript
Lesson 2603 of 2,72352. Linting and FormattingFree lesson

Automation vs. Human Judgment

Recognizing which code quality concerns can be automated and which require human code review.

Automation vs. Human Judgment

What you'll learn: How to distinguish which code quality issues linters can catch automatically and which require thoughtful human code review.

The Limits of Automation

Linters like ESLint are incredibly powerful—they catch unused variables, enforce consistent formatting, flag common mistakes, and ensure your code follows syntactic rules. But they operate on syntax and patterns, not meaning or intent. Think of a linter as a spell-checker: it catches "teh" but won't tell you if your sentence makes sense.

What Linters Handle Well

  • Syntax errors: Missing semicolons, unbalanced brackets
  • Code style: Indentation, quote styles, spacing
  • Common pitfalls: Unreachable code, unused variables
  • Security patterns: Known dangerous patterns like eval()
  • Consistency: Ensuring the entire codebase follows the same conventions

What Requires Human Review

  • Logic errors: Code that runs but produces wrong results
  • Architecture decisions: Whether a function should be split up or combined
  • Naming quality: Is processData() descriptive enough for this context?
  • Business logic correctness: Does this discount calculation match requirements?
  • Performance trade-offs: Is this readable but slow approach acceptable here?
  • Edge cases: Have all unusual scenarios been considered?
  • API design: Are these function signatures intuitive for other developers?

The Balanced Approach

Use linters to eliminate the mechanical burden—let them enforce formatting, catch obvious mistakes, and maintain consistency. This frees up human reviewers to focus on higher-level concerns: "Does this solution make sense? Is it maintainable? Does it solve the right problem?"

Key Takeaway: Linters automate syntax and style enforcement, but humans must judge correctness, clarity, and design quality—automation handles the "how," humans evaluate the "why."