Comment Re:He will be missed (Score 2) 46
The thing about his negative LOC immediately endears him to me.
When I was working at a medical tech company management tried the same thing. Daily report of LOC. I had been hired to refactor and rewrite a terrible bloated piece of PHP hell into something more sane. I realised a lot of its problems had to do with the fact its algorithm was about 4 nested deep layers of for loops with an SQL in the middle (with injection vunls, because of course, PHP) So I refactored about 10 pages ino a page of code and a slightly complicated single SQL query that apparently nobody in the office understood except me for SOME REASON.
Every day was like this and I would put in negative LOC reports in. In the end I got dragged into the bosses office to explain this negative LOC, so I showed him what that was about. And I explained why LOC is a *terrible* metric that fails to account for the fact that in large code bases a coders job is often rejiggering existing code., and if that code is bad, often there will be less code left at the end. And so like in the Atlkinson example management saw the errors of their ways and dropped it altogether opting for a more sane "What did you achieve this week question" (To which I pointed out we used SCRUMM w/ Jira, so they already knew the answer)