Hacker News Reader

On Brownfield software, your LOC counts probably average out to nearly zero. It wouldn't be uncommon to spend four or five hours diagnosing, tracing, reproducing, then fixing and verifying a bug, and the end result would be two lines of code changed when you were all done, with maybe twenty or thirty more in tests.

>I'm honestly curious in what branch of SW development this happens

Most. It is based on some well studied and established averages, anywhere where it's actual core programming (ie. not counting churning out boilerplate html/css/CRUD code N times for the same/same-ish functionality).

Actully 100 lines/day is on the optimistic side:

"Capers Jones has compared many methodologies (RUP, XP, Agile, Waterfall, etc) and programming languages over thousands of projects and determined that programmers write between 325 and 750 lines of code (LOC) per month"

The only people I’ve seen creating more than that consistently have been cut and past programmers that either never heard of DRY or thought it a very contentious principle.