Ask HN: As a developer, do you write 10k-20k lines of code a day? Decided to get some stats for a team project we're working on and got this interesting estimate from Google's AI. Here's an excerpt if you don't care to click the image link: "However, as a general rule of thumb, a senior developer can write between 10,000 and 20,000 lines of code per day." https://imgur.com/a/mSYAq5k As a developer for a couple decades now, not sure I agree with that estimate...not even close to it imo. |
It astonishes me how anyone reads a response like this and then decides to keep using said tool.
This would be like if you went to a restaurant with a friend, with no other customers in it. You order a pork chop with greens.
The waiter returns with a live wild boar, eating a head of cabbage, and you feel the need to ask your companion if it seems wrong.
No, nor would I consider it an improvement if I did.
OTOH, I’ve had some very good days where I net removed 10K+ lines of duplicate, unnecessary, and streamlinable lines of code, and those were very happy days.
30+ years experience.
A more realistic average is 200-400 lines per month. Some sources collected at https://skeptics.stackexchange.com/questions/17224/do-profes...
If you're going for quality, the number will be less. Much, much less. Maybe 100 to 150 lines of code. On a good day.
Just because a chatbot says it's possible doesn't mean it's possible.
I disagree that quantity of lines of code correlate with productivity.
100 lines, tops. On a very good day
I think you can almost press the enter key 10k times per day (I mean, actually pressing, without using repetition) without any meaningful time for thinking what you're writing in a line
If the code is not needed, do not write it.
= "No Code" or Nihilist Software Engineering =
No code runs faster than no code.
No code has fewer bugs than no code.
No code uses less memory than no code.
No code is easier to understand than no code.
No code is the best way to have secure and reliable applications. Write nothing; deploy nowhere.
One of my most productive days was throwing away 1,000 lines of code. -- Ken Thompson
The cheapest, fastest, and most reliable components are those that aren’t there. -- Gordon Bell
Deleted code is debugged code. -- Jeff Sickel
Measuring programming progress by lines of code is like measuring aircraft building progress by weight. -- Bill Gates
= Master Foo and the Ten Thousand Lines =
Master Foo once said to a visiting programmer: “There is more Unix-nature in one line of shell script than there is in ten thousand lines of C.”
The programmer, who was very proud of his mastery of C, said: “How can this be? C is the language in which the very kernel of Unix is implemented!”
Master Foo replied: “That is so. Nevertheless, there is more Unix-nature in one line of shell script than there is in ten thousand lines of C.”
The programmer grew distressed. “But through the C language we experience the enlightenment of the Patriarch Ritchie! We become as one with the operating system and the machine, reaping matchless performance!”
Master Foo replied: “All that you say is true. But there is still more Unix-nature in one line of shell script than there is in ten thousand lines of C.”
The programmer scoffed at Master Foo and rose to depart. But Master Foo nodded to his student Nubi, who wrote a line of shell script on a nearby whiteboard, and said: “Master programmer, consider this pipeline. Implemented in pure C, would it not span ten thousand lines?”
The programmer muttered through his beard, contemplating what Nubi had written. Finally he agreed that it was so.
“And how many hours would you require to implement and debug that C program?” asked Nubi.
“Many,” admitted the visiting programmer. “But only a fool would spend the time to do that when so many more worthy tasks await him.”
“And who better understands the Unix-nature?” Master Foo asked. “Is it he who writes the ten thousand lines, or he who, perceiving the emptiness of the task, gains merit by not coding?”
Upon hearing this, the programmer was enlightened.
Source: "The Art of Unix Programming" by Eric Raymond