How many loc

Ralph M. Rickenbach Ralph M. Rickenbach This formula seems faulty. My current project is 4kLOC after cleanup. A specific LOC took me 2 weeks to learn and write with tons of gotchas i hated that one Does it only apply to lines you have no previous experience with?

It applies to the development of new projects, but includes all phases of a project. It has been established in , so maybe some productivity has been gained. It only applies to teams, not single developers. Good developers are up to 10 times faster than bad ones, so your experience may not apply. One might also take into consideration the definition of LOC: nothing generated, handwritten just statement lines.

And of course it depends on the programming language ASM - C. But is LOC really an interesting meassure for code? LOC may not be an absolute measure of code complexity, but it is a reasonable approximation, especially if you pay more attention to the magnitude than the exact value 1k vs.

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta.

Now live: A fully responsive profile. By comparison, the Microsoft Windows operating system has roughly 50 million lines of code. Of course, every engineer knows that "lines of code" is a silly measure, and besides, the lines of code we are counting here are much less complex than the code written by professional software engineers. No software engineer measures the value or their work in lines of code. In fact, the best-designed programs often have the simplest designs and the fewest lines of code.

However, we count this as an important measure of total usage of our tutorials. Not everybody finishes an Hour of Code tutorial. Some students spend one hour. Some spend 10 minutes. Some spend days. Instead of counting how many students "finish one hour" or how much time they spent, this is our simplest measure of progress.

Note: this is not counting all participants in the Hour of Code. The Hour of Code movement consists of dozens of tutorial partners, and this metric is only counting usage of Code. Small may not accomplish much, but the odds of outright failure-- a disturbingly common outcome for most software projects -- is low. I don't think the inverted, non-linear relationship between size and productivity on software projects will come as a shock to anyone; the guys at 37signals have been banging their drum on the virtues of small for over a year now.

Isn't small the new big already? But what I really want to focus on here is how you measure a project's size. What's big? What's small? McConnell is using lines of code LOC as his go-to measurement.

So you have to be careful that you're really comparing apples to apples.