Riding The Lines-Of-Code Rollercoaster

written by Scott Muc on Wednesday, May 20 2009

Lines of code has always been a poor guide in measuring developer productivity. I'm currently reading Scott Rosenberg's Dreaming In Code and came across and interesting quote.

"Atkinson [ed: Bill] had just completed rewriting a portion of the Quickdraw code, making it more efficient and faster. The new version was 2000 lines of code shorter than the old one. What to report? He wrote the number -2000" -- Rosenberg

I couldn't help but smile when I read that. I have felt that some of my best coding successes are when I eliminate lots of code. This probably pushes Test Driven Development (TDD) as a great practice even further. Lately I've been a bit stricter by doing TDD. This means that I'm writing a lot more code, but as I get my tests passing I start refactoring and remove much of the code that's written. For every couple hundred lines of code I write, I eventually remove 50-80% of it as I glean knowledge from all the code I previously wrote.

It appears that LOC Rollercoaster development is an artifact of TDD and it's a great ride!

Similar Posts

  1. My Developer Resolutions For 2010
  2. My Developer Resolutions For 2009
  3. A New Beginning (or Goodbye 20's, Hello 30's)

Comments

  • Tobin Harris on on 6.18.2009 at 2:30 PM

    Tobin Harris avatar

    Totally agree. Each time I do a "git pull" it shows home code was added and removed from the code base.

    Seeing when developers remove code is always a GOOD THING :)

    I've also worked in shops where removing code is considered more important than adding it. Great mentality.

Post a comment

Options:

Size

Colors