Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×
Programming

+ - Why Coder Pay Isn't Proportional to Productivity

Submitted by theodp
theodp (442580) writes "John D. Cook takes a stab at explaining why programmers are not paid in proportion to their productivity. The basic problem, Cook explains, is that extreme programmer productivity may not be obvious. A salesman who sells 10x as much as his peers will be noticed, and compensated accordingly. And if a bricklayer were 10x more productive than his peers this would be obvious too (it doesn't happen). But the best programmers do not write 10x as many lines of code; nor do they work 10x longer hours. Programmers are most effective when they avoid writing code. An über-programmer, Cook explains, is likely to be someone stares quietly into space and then says "Hmm. I think I've seen something like this before.""
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Why Coder Pay Isn't Proportional to Productivity

Comments Filter:

"Text processing has made it possible to right-justify any idea, even one which cannot be justified on any other grounds." -- J. Finnegan, USC.

Working...