[Scalestein]

I'm all for the 'results based' work environment but I think measuring results of work that you hire people to do IS quite hard.

A great example is refactoring. Say you hired a dev and he delivered a product that worked but is written terribly (already a question there, how do you gauge that in terms of 'results'?). Now you hire a second dev to clean it up and make it maintainable. How do you evaluate when he has delivered the 'results'?

edit: I think the closest thing to a true results based workplace would be an early stage startup. Everyone is invested in the product and striving towards creating it, not just putting in hours. In those cases people usually end up working WAY more than 40 hours a week.

[NoMoreNicksLeft]

> A great example is refactoring. Say you hired a dev and he delivered a product that worked but is written terribly (already a question there, how do you gauge that in terms of 'results'?). Now you hire a second dev to clean it up and make it maintainable. How do you evaluate when he has delivered the 'results'?

Easy. Lines of code.

The first developer did an awesome jobs, many lines of code were written. The second one is a lousy hack, he earned about $50 (not $50k).

This is ridiculous of course, but it does show how even bad measurements are preferred over non-measurement.