Code line counting..
Duncan writes:
From time to time, when I've shown someone a system I built, I've been asked "How many lines of code is that?"... and my answer has always been the same... "I have no idea".
I've never even tried to count the lines of code in a project, and I have no idea why I would. Jason mentions in his post that some people have to account for their lines of code produced in a day and I think that is absolutely crazy. So if you write more lines of code, you are a more productive employee? I hate to point out such an obvious point, but I'd like to think that the important point is how many bugs you fixed or how many features you completed.... regardless of how much typing it required.
I hate the fact that I have to produce a report of lines of code. I totally agree that I should be judged on the quality of code that is produced and not how many lines it took. In fact I've gone as far as intentionally written more lines to solve a problem when I knew it would take less. My boss tells me that it was the best code I've ever written??!? Because it was 200 lines as opposed to 20. WTF?!
I think there is a mentality out there that more is better. Any developer would tell you that's not true ( unless it's money, sex or Mt. Dew ). But until we get more dev's into management *shutter*, I don't know when it will stop. Now of course this is all my opinion and does not represent the views of my employeer ;)
Oh and Duncan, you saved my ass with your DirectoryServices article. Thanks alot!
** Update **
Darren likes PLC...