News for hackers. Stuff that matters.
Re:Are Your Programmers Working Hard, Or Are They Lazy? by markkanof on Thursday December 12, 2013 @12:49PM (#6895817)
I completely agree with your conclusion that almost everyone would like to hire Bricklayer B, but I think the disconnect in most work situations comes in rewarding the value provided by that person. If for example both workers would charge 5000 dollars to build the wall, people would be much more skeptical of paying Bricklayer B, because after all, it was only two hours of work. Basically people still have trouble evaluating the value of the work done vs the effort expended to do that work.
Re:Are Your Programmers Working Hard, Or Are They Lazy? by jmagoon on Thursday December 12, 2013 @03:23PM (#6896939)
This is totally true, and as the original article mentions:

"Unless you can afford to have two or more competing teams solving the same problem, and c’mon, who would do that, you will never know."

So, the above metaphor is almost always impractical, and it's hard to tell what the alternative is to the one bricklayer you have.

Re:Are Your Programmers Working Hard, Or Are They Lazy? by penguindev on Thursday December 12, 2013 @09:22PM (#6898699)
...I wonder how many times competing teams have been used for something? It actually sounds fascinating.

The mythical man month never mentioned that. It mentioned multiple implementations of one architecture, but that was for hardware IIRC.

Re:Are Your Programmers Working Hard, Or Are They Lazy? by zwdr on Friday December 13, 2013 @06:05AM (#6899972)
AFAIK it is used in failsafe systems: you have two systems who deliver the same output, but are developed independently.
Re:Are Your Programmers Working Hard, Or Are They Lazy? by Avenger42 on Thursday December 12, 2013 @02:28PM (#6896469)
It depends - if everyone knew that B would provide a superior wall, in less time, for the same money, then they'd have a choice to make. Do I care about the build quality? Do I care about the time?

A better example is if A now comes back and says "yes, my wall's not as good, and I take longer, but now I'm only going to charge $4000", then you've got a bigger question - is it worth $1000 to you to get a higher quality wall that's done quicker? Or would you rather save the money and lose the time and build quality?

This more easily converts to a software example - do you pay a senior developer to develop your product quickly and well? Or do you save money by hiring a developer of lower skill, who will likely take longer and deliver a lower-quality product?

Re:Are Your Programmers Working Hard, Or Are They Lazy? by deegles on Thursday December 12, 2013 @03:03PM (#6896773)
You're making a key assumption that a person is capable of evaluating the skill of a developer and the quality of the end-result.

What if you have no background in software? If the lower-skill developer convinces you his work is better (even if it's not) you're going to go with him.

Re:Are Your Programmers Working Hard, Or Are They Lazy? by zevyoura on Thursday December 12, 2013 @03:26PM (#6896963)
Even if you do have a background in software, evaluating talent is difficult; it's why the interview process can be so convoluted.
Re:Are Your Programmers Working Hard, Or Are They Lazy? by userulluipeste on Friday December 13, 2013 @09:04AM (#6900489)
"if everyone knew that B would provide a superior wall, in less time, for the same money, then they'd have a choice to make"

I'm more inclined to think that people would try to bargain hard with the Bricklayer B - "$500 in two hours is a good price for you, pal". After all the thought goes that even for that price B can erect a lot of walls in two weeks (which is A's single wall building time-span), and that's... only fair, right?

(in addition) Don't foul yourself that we live only under market-like laws of supply and demand, we're also social creatures that supposedly have to obey social norms. And the norms can be dictated.

Re:Are Your Programmers Working Hard, Or Are They Lazy? by marknutter on Thursday December 12, 2013 @03:19PM (#6896909)
I would hire Bricklayer B on an hourly basis.
Re:Are Your Programmers Working Hard, Or Are They Lazy? by ronaldx on Thursday December 12, 2013 @03:38PM (#6897071)
Bricklayer B now takes 2 weeks as well.
Re:Are Your Programmers Working Hard, Or Are They Lazy? by reginaldjcooper on Thursday December 12, 2013 @06:08PM (#6897923)
I beg to differ, Bricklayer B would reject the job on account of being too busy doing work that paid a sum reflecting the value provided rather than reflecting the sociopathy of the employer.
Re:Are Your Programmers Working Hard, Or Are They Lazy? by hrjet on Friday December 13, 2013 @07:16AM (#6900155)
Or.. B demands a higher payout. That reduces his customer base without affecting his revenue significantly. With fewer customers he has more free time on his hands, in which he invents robots that build brick walls. He now lowers his hourly rate.
Re:Are Your Programmers Working Hard, Or Are They Lazy? by ivanca on Thursday December 12, 2013 @05:29PM (#6897723)
Of course; otherwise he would be punishing himself for his efficiency.
Re:Are Your Programmers Working Hard, Or Are They Lazy? by dreamfactory on Friday December 13, 2013 @09:06PM (#6904218)
Hardly, faster time to market is a value multiplier, not a loss.