4 ms·

Somewhere between 100 and 150. 10 fricking lines? Who produces just 10 lines? Are you just looking at your monitor and day dreaming or what? I just wrote 5 line

Somewhere between 100 and 150. 10 fricking lines? Who produces just 10 lines? Are you just looking at your monitor and day dreaming or what? I just wrote 5 lines of text right now in like 2 minutes.

nostrademons 18y ago
AFAIK the 10 lines/day figure is a long-term average for tested, debugged code in large organizations. If you normally write 100 lines/day, but spend 90% of your days in meetings, rehashing old design decisions, tracking down bugs in vendor's code, debugging that NullPointerException your coworker introduced, and writing tests to ensure it never happens again (or worse, writing memos to pretend it'll never happen again), I could easily see how that'd drop to 10 lines/day. And I don't think that's an inaccurate description of the corporate development process: even in a startup, working with a team of 4 people, I spent more time than I would've liked on the above activities.
icey 18y ago
Yesterday I probably wrote 8 or 9 lines of code. That was all the problem at hand required. However, getting to that 8 or 9 lines of code took hours of conversation with various people as well as a few more hours of research, fact-checking and bench-marking. Last week I had a day where I probably generated 25,000 lines of code. The generator probably took up 400 or so lines itself. Because I wrote the generator, do I get to say that I created the 25k lines? The small amount of code I wrote yesterday was vastly more important that the generated code I wrote last week. Which day was more valuable? Lines of code is a worthless measure. [Edited for tone]
jon_dahl 18y ago
I just wrote 5 lines of text right now in like 2 minutes. Doesn't seem like much of a comparison. Sure, I could write hundreds of lines of code in a few hours (or thousands of lines of text) if my goal was to produce volume. But if my goal is to improve a complex program, it might take 8 hours to complete a 10 LOC change.

Somewhere between 100 and 150. 10 fricking lines? Who produces just 10 lines? Are you just looking at your monitor and day dreaming or what? I just wrote 5 lines of text right now in like 2 minutes.

nostrademons 18y ago

AFAIK the 10 lines/day figure is a long-term average for tested, debugged code in large organizations. If you normally write 100 lines/day, but spend 90% of your days in meetings, rehashing old design decisions, tracking down bugs in vendor's code, debugging that NullPointerException your coworker introduced, and writing tests to ensure it never happens again (or worse, writing memos to pretend it'll never happen again), I could easily see how that'd drop to 10 lines/day. And I don't think that's an inaccurate description of the corporate development process: even in a startup, working with a team of 4 people, I spent more time than I would've liked on the above activities.

icey 18y ago

Yesterday I probably wrote 8 or 9 lines of code. That was all the problem at hand required. However, getting to that 8 or 9 lines of code took hours of conversation with various people as well as a few more hours of research, fact-checking and bench-marking. Last week I had a day where I probably generated 25,000 lines of code. The generator probably took up 400 or so lines itself. Because I wrote the generator, do I get to say that I created the 25k lines? The small amount of code I wrote yesterday was vastly more important that the generated code I wrote last week. Which day was more valuable? Lines of code is a worthless measure. [Edited for tone]

jon_dahl 18y ago

I just wrote 5 lines of text right now in like 2 minutes. Doesn't seem like much of a comparison. Sure, I could write hundreds of lines of code in a few hours (or thousands of lines of text) if my goal was to produce volume. But if my goal is to improve a complex program, it might take 8 hours to complete a 10 LOC change.