Global Commenting

Self-documenting code uses clear, descriptive variable and function names combined with explicit structure to convey intent without extraneous comments. Focus on naming that reveals purpose—`calculateTaxAmount` instead of `calc`—and organize logic into small, single-responsibility functions so the 'what' becomes obvious from reading the code itself.

Add comments only to explain non-obvious business logic, complex algorithms, or architectural decisions—the 'why,' not the 'what.' Comment tax calculation edge cases or regex patterns that aren't immediately clear. Avoid narrating every line; let clean naming and structure speak for themselves.

Yes. Self-documenting principles—clear naming, explicit structure, and strategic comments—apply across all programming languages and file types. Whether writing Python, Java, or JavaScript, the same practices improve readability and maintainability.

Review code by checking that variable names are descriptive, functions have single purposes, and comments explain only complex or non-obvious logic. Refactor unclear naming, break apart tangled logic, and remove redundant comments that simply repeat what the code does.

'What' comments repeat the code's action—redundant and harmful to maintenance. 'Why' comments justify design choices, business rules, or non-obvious approaches. Comments explaining 'why we calculate tax before discount' are valuable; comments restating `x = x + 1` waste space and go stale.

Yes. Apply self-documenting principles during refactoring by renaming variables for clarity, restructuring logic into smaller functions, and replacing obsolete comments with clearer code. This technique improves readability across new code, reviews, and maintenance tasks.