Hard to say. But I've written 93 lines of Haskell code today. I'm new to Haskell so I've spent most of the day refactoring the same code. If we say I've written 93 lines per day since the 1st then that would total to 1116.
Name:
Anonymous2008-01-12 2:11
I write maybe a couple dozen klocs, but code generated many, many more.
>>50
If microsoft asks how many loc you wrote last year, you answer. They're not trying to assert your productivity. Only the number of loc you wrote
Name:
Anonymous2008-01-12 8:30
>>51
``I wrote 0 lines of code, that makes all my program secure, also it makes me a bad programmer according to you. When you'll fire me, people will know you did because none of my programs had a single bug.''
Name:
Anonymous2008-01-12 10:01
>>51
If microsoft asks how many "loc" I wrote last year, I wipe my arse with their fat faces.
Name:
Anonymous2008-01-12 10:22
>>53
That's cute, considering that you're still in your first year of college and never had a job programming anything.
Name:
Anonymous2008-01-12 10:25
>>54
That's cute, considering you're an enterprise faggot and never had a job programming anything.
>>54
That's cute, considering I'm an experienced programmer from the dotcom era and you'll be polishing my shoes and calling me "sir" in your first job that does not involve shelves or deepfrying.
Name:
Anonymous2008-01-12 11:50
>>58 considering I'm an experienced programmer from the dotcom era
So you're begging for change in the subway now?
I have no interrest in keeping useless and arbitrary statistics like LOC, and I couldn't even begin to guess. I'm doing some maintenance too, so I'd guess I'm removing about half as much code as I'm adding. Pointless metric is pointless.
Name:
Anonymous2008-01-13 7:14
Opps. I'm >>46 I read it as '2008'. In 2007 it would be thousands of lines of code.
10, surprisingly enough it was not a good year employment wise
Name:
Anonymous2008-01-13 10:05
>>76
I wouldn't hire a programmer who only writes code on the job.
If he doesn't enjoy programming, he's not going to be any good, and if he did enjoy programming, he'd code in his spare time.
Name:
Anonymous2008-01-13 14:56
putStrLn considered harmful, use putStr instead.
Name:
Anonymous2008-01-13 15:07
>>78
I'm surprised that's all anyone noticed. The `.' used would make a type error. The code should've been: do contents <- readFile "filename"
putStr contents
Name:
Anonymous2008-01-13 15:25
>>79
ONE WORD, LACK ON INDENTATION OF THE CODE, THREAD OVER.