.
How Many Lines Of Code Did You Write Today ?
FORMAT: <Language>, <number of lines>
.
Lisp, 82
.
Java, 186
(I'm productive on Saturdays :( )
null, 0
Saturday!
.
Lisp, 19
.
How many did I want to write? Lots!
How many did I actually write? None!
It can be argued that I am making a game using Unity. If you define 'am making' as 'have not started but have written extensive designs for'.
.
Perl, 53
.
3
Visual Basic, 112
.
Lisp, 11
Visual Basic, 49
.
.
Lisp, 24
.
|
| 2 people marked this as a favorite. |
OK - we've had our fun. A few questions:
1) With all that code, how many lines of comment did you write? How much documentation?
2) Does anybody think "number of lines of code written" is a useful metric?
On a couple of occasions over the years I've spent a large amount of time (days - sometimes weeks) tracking down and replicating obscure and/or intermittent bugs deep in the bowels of large and complex systems. In two of the toughest challenges the eventual solution turned out to be a very minor code change, modifying a single line of code (in fact in one case it was modifying a single instruction in an assembler source file). The last time I did this I was working (indirectly) for HP, and we did have to track these sorts of figures. My immediate boss and I took great satisfaction in reporting to HP that I had spent slightly over two weeks to generate a single line of code. As we noted, it wasn't changing the line of code that was important - it was knowing which line to change.
.
Lisp, 53
.
.
Lisp, 16
.
.
Lisp, 96
.
.
Lisp, 65
.
.
Perl, 153
.
.
Perl, 21
.
|
1) With all that code, how many lines of comment did you write? How much documentation?
In the case above, there was no comment or documentation. It was a fairly simple image upload function. That said, I did copy/paste in a comment from a text document I have where I keep all my comments, just in case someone else has to use my code, after I'd written the actual code.
I wrote a note to my local organizer using lemon juice and a code involving a 1983 issue of Playboy.
Does that count?
.
Lisp, 18
.
.
Visual Basic, 62
.
.
Visual Basic, 239
.
|
I don't really count. This is pretty subjective anyway. I tend to write shorter lines of code than most people, so I tend to get more lines out of the same code. I've had people come to me and ask for help debugging something where all their lines of code are 100-200 characters long, and the first thing I do is break up the clauses into shorter lines to make it easier to read.
.
Perl, 154
.
C++ aprox 200
|
|
I used to work for a company that still used Cobol as their primary language when I left them 4 years ago, and I doubt that's changed since. I learned how to skim it to figure out when variables are getting set, for trouble shooting purposes, but I never learned all the details of the syntax to be able to write it. But I was also working support, not a programmer.
.
Lisp, 3
.
| 1 person marked this as a favorite. |
Last night I dreamed I was coding a pointer-based linked list for a procedural mapping program. It seemed pretty coherent and I got reasonably far before I woke up.
.
Lisp, 57
.
.
Lisp, 52
.
Final project rush last weekend lead to a lot more java gui than I'd ever want to do ( >0 )
I don't even know how many lines.
Inspired by this thread, I went to our subversion server and pulled out some stats:
I have touched 578,495 lines of code between 1/4/11 and 11/12/12. That works out to an average of 853.2 lines of code per day, including weekends and holidays.
A lot of that is inflated by auto-code written by the Visual Studio designers, and it includes a lot of changes to existing code rather than new lines from scratch, but I'm pretty sure I'm being conservative in saying that I'm likely to touch over 200 lines of code on a slow day.
but I'm pretty sure I'm being conservative in saying that I'm likely to touch over 200 lines of code on a slow day.
And ironically enough, today I maybe wrote 100 lines tops, because I spent all afternoon trying to set up 3rd party shipping software. Two and a half hours wasted to an extra "-"...
.
C, 36
.
.
Visual Basic, 86
.