What LOC stats mean
Lines of code (LOC) is the classic project-size metric — flawed but useful for estimates, code review load and "how much did we write". The useful split is code vs comment vs blank: high comment ratio often means a complex or well-documented file; high blank ratio suggests poor structure; a huge code count in one file is a refactor signal.
How the counting works
- Code lines — non-empty lines that aren't comments.
- Comment lines — full-line comments plus block-comment content (C-style
/* */or Python triple-quoted strings, per the picker). - Blank lines — whitespace-only.
- Inline comments (code + trailing
//) count as code — matching tokei/cloc behavior.
Real-world use
- Estimating effort: experienced devs write ~100–300 LOC/day net in mature codebases.
- Code review: a 1000-line file needs splitting more than a 100-line one, regardless of quality.
- Pair with the Word Counter for docs, or the SQL Formatter when tidying before the count.