Live data from Hacker News

Why programmers are not paid in proportion to their productivity (2009)

johndcook.com

71–72 of 72 posts

Re: Why programmers are not paid in proportion to their productivity (2009)

#71
post #59

Earlier quoted context omitted.

What do you see/what do you think he does differently compared to the rest of the team?

Really, I don't know. He's tried to mentor others but whatever he tells them doesn't "stick". He might be more intelligent than others, and he is intelligent. He could just make better, faster connections constantly. Maybe he just listens to the inner voice and types whatever comes out. When you ask him, he just shrugs and says he does his job.

If you start solving highly abstract problems (including chess) before you're eight years old, that helps. Deciding you're going to become a concert pianist at eighteen doesn't work if you haven't picked up an instrument before then. You can become a pianist, but not a concert pianist.

Re: Why programmers are not paid in proportion to their productivity (2009)

#72

Like many “preventative” things, it can be hard to prove that problems would have occurred with less experienced/productive people because you only have one team and outcome in any situation. And there’s a lot of easy-sounding ways to “measure” quality that actually suck (e.g. “number of bug reports” says nothing about the kinds of bugs, and might encourage people to create micro-bugs to inflate numbers or mega-repor…

Right. When the company dies or goes down for some while, you may be able to identify the minus-ten-times employee who allowed that to happen. But he's likely long gone by then.
Post reply on HN