24 ms·
>programming, where a rate of say 100 lines per day is a major achievement Wait, what? 100 lines per day is an achievement? I'm honestly curious in what branc
by why_Mr_Anderson 6y ago
>programming, where a rate of say 100 lines per day is a major achievement
Wait, what? 100 lines per day is an achievement?
I'm honestly curious in what branch of SW development this happens. I'd assume something that requires formal proof of every piece of code ever written?
- thrower123 6y agoOn 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.
- coldtea 6y ago>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"
- Ma8ee 6y agoThe 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.