3 ms·
The one caveat is that git has a somewhat more expansive view of what counts as a rewrite of a line of code than what would be counted as a rewrite when writing
by koboll 8y ago
The one caveat is that git has a somewhat more expansive view of what counts as a rewrite of a line of code than what would be counted as a rewrite when writing a book.
- sarreph 8y agoSometimes I pat myself on the back too quickly before realising more than half my line ‘contribution’ is from package-lock.json :)
- antoineMoPa 8y agoUnindent 1000 lines of code after removing a if() statement. You just changed 1000 lines of code in 2 seconds. Reformat entire file automatically with editor, you just changed 4000 lines of code.
- weeksie 8y agoHoly crap, what are you working on where 4kloc files are the norm? (and 1klock if statements. . . .)
- antoineMoPa 8y agoI put some exaggerated examples in there to show situations where changed line counts are absurd (when whitespace is counted). Such numbers of whitespace changes do not happen often, but have a big impact on LOC when measuring a long period of time. I realized that when counting my changed LOC for a past internship.
- NegativeLatency 8y agoI’ve seen that before. Stayed at that job for 4 months before realizing the other engineer was just going to keep writing the same crap. No tests, no comments. The real kicker was that the “database” was several different instances of mongo. So doing joins was a pain, and having transactions was almost impossible.
- Cthulhu_ 8y agoYeah I wouldn't mind a new system that can analyze git history and accurately count changes - not counting package.lock changes, indentation / reformatting, snapshots, etc.