Timeline for Are there known valid uses of SLOC to measure productivity?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 20, 2017 at 20:24 | history | edited | Frank Hileman | CC BY-SA 3.0 |
added 234 characters in body
|
| Nov 20, 2017 at 5:16 | comment | added | Frank Hileman | @ArseniMourzenko Aside from jokes like Brainfuck, well designed languages are actually compared on the basis of the amount of code needed to solve a task. Usually such a comparison is called expressiveness. It is true though, I was talking about LOC within a single language, not across languages. Productivity is generally defined as how long it takes to perform a task; that is not specific to programming. | |
| Nov 19, 2017 at 23:06 | comment | added | Arseni Mourzenko | This could be a valid point if we were comparing the productivity of individual developers. The question is however about the comparison between languages, so the context is very different. This also means, for instance, that smaller code is not better or worse than larger code; compare LOC of code written in Brainfuck with code written in, say, Ruby. | |
| Nov 19, 2017 at 22:56 | history | answered | Frank Hileman | CC BY-SA 3.0 |