4 ms·
I read this somewhere on HN a while back "Pay a man by the hour and he will put in as many hours as he can, Pay a man by the brick and he lay down as many brick
by kamaal 15y ago
I read this somewhere on HN a while back "Pay a man by the hour and he will put in as many hours as he can, Pay a man by the brick and he lay down as many bricks as he can".
I would go on to add and say, If you a pay people flatly some will work, some won't and rest will do mediocre. The guide to get work done is to drive the rewards in that direction.
I fail to understand what stops companies from paying people on the basis of work done, rather flatly or hours spent. Is it because it will set a dangerous precedent and that productive people will end up earning more than what you expect to pay?
I refuse to believe that people are not motivated by money or that money is somehow not a major motivating factor. All passion, determination et al management talks is OK. But I'm not happy earning less than what I'm supposed to. Just because I could it doesn't mean I should. I do more than everybody else back at work, so I obviously I deserve more.
The way salaries work is to get bulk of the work from a few. But then reward every body equally on a average basis. That to me seems like expecting a few to carry a burden of the whole lot. And has a strong stench of communism to it.
- whatusername 15y agoTo quote from the article: "This is the base salary. To participate in the company's profits, we also have a generous profit sharing program as well."
- wpietri 15y agoAt least with software, productivity is very hard to measure without introducing perverse incentives. This is especially true at small or innovative companies, where people must be flexible. Moreover, software is creative work, not brick-laying. There's a fair bit of evidence that incentive schemes harm that work. (See "Punished by Rewards" for details.) I code because I love it. If it didn't pay, I'd be like my actor/musician friends and get a day job. So I just want my salary to be livable and fair. I don't really care about maximizing it.
- kamaal 15y agoYes, Even I love to code. But just because true hearted altruistic people like you exist. It doesn't mean I must replicate the same. I'm motivated by many other factors apart from money. But just because that is the case, I feel no reason to settle down for less than what I deserve. And just like you mentioned I want my salary to be just fair. Just pay me for my work. That's all I'm asking. And is that a unjust demand?
- wpietri 15y agoI'm all for fair. I just think incentive systems are a bad approach to that for programmers.
- lutorm 15y ago"what I deserve"? Your demand is not unjust, it's meaningless. This is not some god-given court that determines what you "deserve". You say that you are motivated by money and other factors. So then the question is: If job A pays x and gives you the other factors that you say motivate you, and job B pays y but gives you none of those other factors, what is the minimum ratio of x/y for you to take job A over B? If you say 1.0, then no, those other factors do not matter to you. If it's <1.0, then why is it not "fair" for the job A to pay that?
- kamaal 15y ago>>>This is not some god-given court that determines what you "deserve". Well in that case let karma decide for itself. Now lets come to what you are talking about. I guess you didn't understand me. I was asking why is it that employers for people under the same conditions pay the same money for different work delivered? What you are saying is true, but that is a totally different question in itself. What you saying is to consider a trade off between other factors and money in two different setup and is perfectly acceptable. But that's not what we are debating here. We are debating why some who is doing a lot more extra is getting paid the same as some who isn't doing all that. In that case I don't see any reason why the first person shouldn't make extra. I would go to an extent to say he doesn't just deserve but has the right to make that something extra.
- mattmanser 15y agoThe problem with this idea is that it's very easy to incentivize the wrong metric. What are you going to do for a programmer? Feature? Prepare for features that barely meet the spec and nothing else. Lines of code? Prepare for massive code bloat. And all of these will also mean no-one will bother with internal tools or any quality of life clean ups. Refactoring will be avoided. Helping other people will mean earning less money. There's also research out there that shows this is a bad idea. This type of incentivization has negative effects on productivity in our type of work. People won't say no to more money, but it doesn't make them work better. Your final paragraph highlights bad management, not communism. If you've a few stars and a lot of mediocre then your management has failed. Be it their hiring, their day-to-day management, their personal development of their staff, their lack of challenging work, poor planning, whatever it is it's not expecting a few to carry the burden, it's letting a few carry the burden because of bad management.
- kamaal 15y agoI disagree here, There is good enough metric for your 'work', its wealth generated at the end of it. Many even refer to it as value created. Again I know the next question you will ask is what if the person worked hard and still fail. Well that is not going to be often. Team work is every body working to achieve something. One set of people making up for other peoples inefficiency isn't team work. I am not telling people must be paid more money to motivate them, I am saying.. We must ask people to work more to earn more money. Which is perfectly acceptable. I don't know why I should earn equal to some guy sitting next when I do far more than what he does. Again counter argument to that which people put is, that putting in extra effort is personal choice so it shouldn't be compared. Well in that case, the other argument is also valid. If some one chooses to be inefficient its his/her problem.
- AlexandrB 15y ago> There is good enough metric for your 'work', its wealth generated at the end of it. In a company larger than a startup, this is usually outside the employees control. A project with a small (or no) market, isn't going to make a lot of money, even if it was a lot of work to create. The people assigned to work on such a project may not be there by choice. Also, what about "internal" projects that don't actually generate revenue, but make everyone more efficient?
- Duff 15y agoThat concept just doesn't work for knowledge workers. Cash incentives for non-mechanical tasks have minimal value. You need to pay people enough, but not too much. The rest is about having leadership in place that can create a good work environment. If compensation was correlated to performance, industry would have figured out a way to pay for performance and let the people doing nothing go.
- lutorm 15y agoAlso frequently referenced on HN is the TED talk about how monetary rewards lowers performance in creative endeavours. People in creative jobs are not simply monetary-maximizing machines. They will work hard if their work is interesting and rewarding in all kinds of non-monetary ways. (I also assume that what they think is that if you don't like the work, you'll leave and find one you like better, or that pays better. So you don't get people who don't like the work, don't do a good job, but will try to hang around as long as possible because it pays so well.) Besides, I agree with the other posts that any practical scheme for paying programmers for performance will be subject to issues of "optimization by proxy". Just look at finance: there, where you'd think it would be easier than most other fields to measure "the wealth generated" by people, all that apparently happens is that you incentivize short-term gain at the cost of assuming huge long-term risks.