News for hackers. Stuff that matters.
Re:AWS Java documentation is fucked by hoodoof on Friday February 12, 2016 @11:25PM (#11092535)
Sorry I challenge this notion. I don't believe anyone gets paid by the line of code. Even Java programmers.
Re:AWS Java documentation is fucked by orbitingpluto on Friday February 12, 2016 @11:50PM (#11092599)
Well not anymore at least. Streams and lambdas wouldn't be implemented if that was the case.
Re:AWS Java documentation is fucked by Turing_Machine on Friday February 12, 2016 @11:42PM (#11092580)
Individual programmers may not (although it's certainly used as a bogus "productivity" metric in many companies) but shops do.

Most famously, IBM insisted on paying Microsoft by kLOC for their work on OS/2, and we all know how that turned out.

Re:AWS Java documentation is fucked by hoodoof on Friday February 12, 2016 @11:55PM (#11092609)
I knew this is what you were referring to. That was a long time ago.
Re:AWS Java documentation is fucked by myhf on Saturday February 13, 2016 @01:30AM (#11092883)
It would be foolish to explicitly pay for lines of code, but there are lots of situations where that happens implicitly.

Most programmers get paid by the hour, and consistently produce about the same number of lines of code per hour.

Most large contracts are billed according to the perceived magnitude of the task. The value to the client is more important than the cost to the contractor, but the cost is still a factor. And for a contractor who has already decided which programmers will work with which tools, that cost is directly proportional to lines of code.