Optimize for lines of code not written! Good programmers can optimize this metric by quite a lot -- hence LOC count means absolutely nothing. It is better to t

Optimize for lines of code not written! Good programmers can optimize this metric by quite a lot -- hence LOC count means absolutely nothing. It is better to think for a long time about a problem and then only write the 20 lines that solves it rather than throwing 300 lines at the problem and still sit with a flaky solution. insert rant about test-driven-design-fanatism here. At the moment I am cranking negative lines of code count in the project I am working on. The code is not that good and can be abstracted quite much, so I am overall removing lines from the code via the rewrite. Interestingly, there is also the quality of said cranked lines. It isn't good when the lint tool finds problems or when the code produced just looks damn ugly.