First off, from MySQL.com this morning - they have released the latest development version of their amazingly popular database server (back on the 1st, but oh well) - and have it availible for download from their download pages as well as a Changelog for the differences between versions. Please note, this is not a stable release, but a development release. Thanks to Steffen for pointing this one out...
And, secondly , from the fine folks at Builder.com we have a new article that talks about counting lines of code to help measure progress. Basically, it's one developer's idea that has changed over time about counting the lines of code that someone produces as a measure of their productivity. At first, her believed that it was a bad thing to just count the lines since quantity != quality, but over time, his opinion changed.
Also, I realized that my resistance to counting the lines of code I produced was not based on facts but rather on the feeling that I would be considered less productive if I spent time on design, meetings, and so forth. But when I gave it more thought, it seemed silly not to count lines of code.
Overall, I think I'm still in his first frame of mind. Yes, I can understand his point that lines of code sometimes can be a good gauge of how much work is being done, but I know enough of my code and enough about my style of coding to know that it's not all about quantity - there has to be a balance.











If I invent an algoithm to do something that takes currently 20 lines of code but mine does it in 3, am one seventh as good as the 20 line developer? Assigning 20 variable to 20 other variables is 20 lines of code, writing a chatroom may be 20 lines of code if there are objects available for re-use, but no matter how much code for reuse there is, it will take longer to code the chatroom and test it.
Lines of code also have to be bug free. So 20 lines of variable assignments can be tested in minutes. A chatroom will take days.
the most effective programmers are those that create new code - new algorithms, new ways fo doing things - how can you measure what they contribute in lines of code? If you run a truly OO shop, a great deal of time will be spent building object libraries, one good object could save many years of effort - how does code counting measure that?