Comments on: Lines Of Code – Dispelling The Myths

By: Let Better Our Health

Let Better Our Health — Mon, 26 Sep 2011 10:34:58 +0000

I wanted to compose you this very little remark to say thank you yet again for those superb concepts you have shown in this article. This is simply pretty open-handed with you to grant extensively exactly what a number of people might have offered for sale for an e book in making some dough for their own end, mostly now that you could have done it if you desired. These basics likewise served as the good way to fully grasp some people have the identical dream just as my own to figure out somewhat more with reference to this issue. I\\\\\\\\\\\\\\\’m certain there are lots of more pleasurable situations ahead for individuals that start reading your blog post.

By: Let Better Our Health

Let Better Our Health — Mon, 26 Sep 2011 10:27:38 +0000

Needed to post you this bit of note to help say thanks a lot once again about the unique things you\\\\\\\\\\\\\\\’ve discussed above. It\\\\\\\\\\\\\\\’s certainly particularly open-handed of you to provide publicly exactly what a number of people would\\\\\\\\\\\\\\\’ve advertised for an e book to help make some profit for their own end, most notably given that you might well have tried it if you ever desired. The tips in addition acted to become easy way to fully grasp someone else have similar interest just as my very own to realize more and more with reference to this condition. Certainly there are a lot more pleasurable instances up front for individuals that see your site.

By: winter boots

winter boots — Wed, 21 Sep 2011 03:21:32 +0000

Thanks for sharing. A real lot of useful info here!

These are all great comments here. Very cool article.

By: beats headphones

beats headphones — Mon, 27 Jun 2011 03:17:01 +0000

Thanks for the marvelous posting! I genuinely enjoyed
reading it, you can be a great author. I will ensure
that I bookmark your blog and will eventually come back
from now on. I want to encourage continue your great
job, have a nice holiday weekend!

By: gianmarco lorezi shop

gianmarco lorezi shop — Sat, 21 May 2011 09:18:42 +0000

Have you ever considered creating an e-book or guest authoring on other blogs? I have a blog centered on the same subjects you discuss and would love to have you share some stories/information. I know my viewers would value your work. If you’re even remotely interested, feel free to send me an e-mail.

By: Nick

Nick — Sun, 30 Aug 2009 03:40:23 +0000

As a REBOLer, I often find the # of lines of code in my projects laughably small. Here’s a full GUI FTP app in only 133 characters only native code (no external libraries). Use it to browse, click to open, edit, and save changes to any file on your web server. The FTP url does not need to be included in the code, and you can add/change paths and file names in the text field while the program is running. If you enter a file name that doesn’t exist, a new file will be created:

u: :to-url view layout[p: field"ftp://user:pass@yourwebsite.com/"[either dir? u v: value[f/data: read u v show f][editor u v]]f: text-list[editor u join p/text value]]

1 line :)

By: Patrick Smacchia

Patrick Smacchia — Thu, 19 Jun 2008 12:27:24 +0000

an easy an umbigous way to count LOC:
http://codebetter.com/blogs/patricksmacchia/archive/2007/10/03/how-do-you-count-your-number-of-lines-of-code-loc.aspx

By: Satya Narayan Dash

Satya Narayan Dash — Wed, 09 Apr 2008 04:09:04 +0000

LOC of code is always about estimation. An estimation (the name is “estimation”, not “final effort” or something like that) can be Order of Magnitude, Finite, Rough, Wet Finger type. And also it depends on which stage of the project you are in and what expertise you have.

At the same time LOC is never used for estimation in a standalone way. It is via Baselining Techniques or COCOMO model.

For LOC, SEI has specified which will be considered to be part of counting and which can not be. And again, your organization may have some different way of calculation also.

You can have a look at:

http://art-of-project-management.blogspot.com/2008/03/estimation-technique-lines-of-code.html

However, havin said all these, bottom line is what kind of engineers you have, what kind of expertise you have and above all the committment to work. Nothing can beat that.

And may be that is reason why so many IT project (read project management) which are not in good shape even with proliferation of so many tools/techniques.

By: nWizard - Norbert Rakosi’s blog on Free Software development … JAVA … Personal Development… and … bad speling… » Clear Simple Code vs Clever One-Liners

Wed, 02 Apr 2008 06:22:13 +0000

[...] I found a nice article (actually the article found me…) written by Alexander Lucas titled Lines Of Code – Dispelling The Myths about a common project management error, which makes estimations and worse makes the evaluation of [...]

By: Simon Brooke

Simon Brooke — Fri, 28 Mar 2008 10:36:20 +0000

I have a project that I’ve been working on with one other guy for about three months. We had a discussion about how many lines of code we’d produced. He guessed about 3,000. I guessed about 300,000. wc said more than 700,000. So what’s going on?

In this project we are automatically parsing the schema of a large legacy database into a custom XML format, and then using XSLT to generate model and controller classes and Velocity macros for views to create a classic MVC application (in C# and Monorail, but actually that makes little difference). So very few of those lines of code are actually hand-written.

And that provides an interesting sidelight into the lines of code debate in more than one way. What are the ‘source lines of code’? The roughly 3,500 lines of sed script and XSL transforms which I actually wrote, the roughly 66,000 lines of the (automatically derived) database schema, or the 700,000 plus lines of C#, Velocity, NHibernate and other stuff which they generate?

If I hadn’t written the auto-generators, that code would still have to have been written (we might have been motivated to write it more tightly, but it would still have been in hundreds of thousands of SLOC). So the number of lines of code you actually write is not a good measure of project size, and the number of lines of code produced is not, either.

And remember, this is happening all down the software stack. I use XSL-T to generate Java, C# or some other high level language. The compiler takes that high level language and in an analogous process generates what in BCPL we used to call ‘CINT Code’ – machine instructions for a virtual machine. The run time system takes the CINT code and generates machine instructions. And inside the processor, the microcode interpreter takes those machine instructions and uses them to generate actual machine operations.

At each stage in the process, the number of discrete statements increases. Which should you count? Why? Even at the level of a binary, a larger binary does not necessarily deliver more functionality than a smaller one.

The other thing is, where a mechanical process is generating code, fixing one bug in the generator will fix hundreds or even thousands of bugs in the generated code. So my hunch is that while functionality scales more-or-less with the number of generated lines of code, bugs scale more or less with the number of lines of code in the generator.