Useless code metric: Yearly revenue per line of code

The world is full of useless code metrics so I thought I would add one of my own I even found someone talking about revenue per line of code.

So what is the yearly revenue of the product you're working on divided by lines of code? You can choose any method you like to count LOC, it's not like we're being scientific or anything.

If this gets enough responses I'll build some graphs.

Please put the number as the first part of the answer to help processing.

From stackoverflow

• 34.59

  We've got a pretty big customer base.

  Andrey : it should be easy to calculate now, how much the customers pay for lines with defects :)

• Even the revenue for the contribution of one programmer is debatable. Maybe the feature you worked on accounted for 10% of sales, maybe 70%.

  The Trap (documentary) is a nice corollary to this kind of post.

  Motti : I'm talking about the whole product not any one person's contribution to it.

• 0 The project im working on have not created any revenue yet... I really hope this number will be much higher(much much) next year

• Hmm, by implementing stuff in-house we have eradicated an expensive external annual subscription product, reduced the cost of using the tool (halved the fees to an external agency that the product interacted with) and improved automation (over the poor annual subscription product) enough to cut a number of jobs. There isn't a value I can put on things really (I don't know the wages of the eradicated positions, etc, and costs are also lower because business is lower because the economy is crap).

  Eclipse Metrics plugin tells me that this project has some 20k lines of code (excluding comments I assume). I'll assume it's saving £200k a year as a reasonable minimum. That makes some £10 per line of code saving, per year. Note that this year that code will be used on an additional new product that will bring in money, and hence should be a factor for income as well as a theoretical cost saving over using the old system for the new product.

  It's a stupid metric because it doesn't count the hours taken to implement, the wages of the programmer and the business analysts, the meeting hours, etc. Should I factor in the lines of code in JSPs, ANT build scripts, etc? Lines of documentation and commenting?