-2000 Lines of Code (2004)
folklore.org
-2000 Lines of Code (2004)
1–10 of 54 posts
Re: -2000 Lines of Code (2004)
#2I love the feeling after having rewritten some code part with the results of having it much shorter, much clearer, more stable and even faster. :) In almost all cases, it was worth it.
The strange thing is, sometimes there are multiple iterations of this on the same code part (sometimes by different people, sometimes even by my own).
Then I am thinking, maybe I just have gotten wiser, have learned my lesson or whatever. Stupid me that I haven't implemented it in the first place like this.
Also, I am always wondering, how much more iterations are there until I get to some final, perfect, optimal solution.
Or will I really end up with one single line of code in the end? :)
Re: -2000 Lines of Code (2004)
#3I love the feeling after having rewritten some code part with the results of having it much shorter, much clearer, more stable and even faster. :) In almost all cases, it was worth it. The strange thing is, sometimes there are multiple iterations of this on the same code part (sometimes by different people, sometimes even by my own). Then I am thinking, maybe I just have gotten wiser, have learned my lesson or whatev…
All code can be made shorter. But all code also has at least one bug. So eventually your code will be just one byte - but it will be the wrong byte :-)
Re: -2000 Lines of Code (2004)
#4Google Cache[1].
Reminds me of that TDWTF post where engineers were paid based on the amount of lines of code they had written - led to massive comment blocks explaining the simplest things ("This is a for loop that works by...").
[1]: http://webcache.googleusercontent.com/search?sourceid=chrome...
Re: -2000 Lines of Code (2004)
#5Google Cache[1]. Reminds me of that TDWTF post where engineers were paid based on the amount of lines of code they had written - led to massive comment blocks explaining the simplest things ("This is a for loop that works by..."). [1]: http://webcache.googleusercontent.com/search?sourceid=chrome...
There's this one: http://thedailywtf.com/Articles/Productivity-20.aspx
where a guy boosts his line count by writing a program convert loops into goto spaghetti (pretty much like the generated assembly, right?).
But has anyone here actually been evaluated in this way? I've never heard about it first hand - it almost seems like an urban legend.
Re: -2000 Lines of Code (2004)
#6The only thing better than writing code is deleting it.
Re: -2000 Lines of Code (2004)
#7“If we wish to count lines of code, we should not regard them as 'lines produced' but as 'lines spent'"
- Edsger Dijkstra
Re: -2000 Lines of Code (2004)
#8I reported to a manager that attempted to measure our productivity fixing bugs by comparing the lines of code before and after the fix. Most fixes reduced the lines of code, so our numbers were usually either negative or close to zero. A couple weeks later the manager interrogated the team as to why we were so unproductive.
Another fun experiment is to measure developers using lines of code, and then switch to unit test coverage. For some reason, the code always seems to shrink.
Counting lines of code for maintenance work is a little like evaluating your mechanic based on the weight difference of your car before and after he fixes it.
Re: -2000 Lines of Code (2004)
#9I reported to a manager that attempted to measure our productivity fixing bugs by comparing the lines of code before and after the fix. Most fixes reduced the lines of code, so our numbers were usually either negative or close to zero. A couple weeks later the manager interrogated the team as to why we were so unproductive. Another fun experiment is to measure developers using lines of code, and then switch to unit t…
Counting lines of code for maintenance work is a little like evaluating your mechanic based on the weight difference of your car before and after he fixes it.
I love this comment.
Re: -2000 Lines of Code (2004)
#10I love the feeling after having rewritten some code part with the results of having it much shorter, much clearer, more stable and even faster. :) In almost all cases, it was worth it. The strange thing is, sometimes there are multiple iterations of this on the same code part (sometimes by different people, sometimes even by my own). Then I am thinking, maybe I just have gotten wiser, have learned my lesson or whatev…
If you look at programming as a knowledge acquisition activity instead of a code production activity, then you couldn't possibly have implemented it that way in the first place.