- 263comments
- 250comments
- 44comments
- 5comments
- 68comments
- 271comments
- 54comments
- 58comments
- 78comments
- 12comments
- 61comments
- 246comments
- 182comments
- 15comments
- 5comments
- 177comments
- 19comments
- 25comments
- 4comments
- 54comments
- 201comments
- 5comments
- 91comments
- 40comments
- 1comments
- 16comments
- 186comments
- 3comments
- 152comments
- —discuss
Actually this might prove the opposite. The intention is of course that his removing of 2000 lines of code while improving behavior is a good thing. Therefore a change in number of lines of code is significant. Therefore you should track lines of code. I track lines of code to get a sense for when there's more lines of code than seem necessary so I can go chopping it away until it becomes manageable.
I do a similar thing on a file by file level. Once a file or single function grows too long, it is time for a refactor.