<story><title>Stop Working All Those Hours</title><url>http://blogs.hbr.org/hbsfaculty/2012/06/stop-working-all-those-hours.html</url></story><parent_chain><item><author>dsr_</author><text>The article is aimed at the wrong people. Corporate culture starts at the top. Stop judging your employees by the hours they appear, and judge them on results. If you can&apos;t measure results, you were in trouble already.</text></item></parent_chain><comment><author>simplezeal</author><text>I should add to that - not just results but quality of results. Software development is a tricky profession to measure for quality - outside of bug count (which may be heavily influenced by quality of testing) and code coverage numbers (those can miss some really nasty edge cases) the only thing you can measure is how long it takes to make change to existing code.&lt;p&gt;I have seen numerous cases where the person implementing the code is rewarded and next one comes along, and rewrites the code since first one is too hard to change. He gets rewarded too and cycle continues.</text></comment>
<story><title>Stop Working All Those Hours</title><url>http://blogs.hbr.org/hbsfaculty/2012/06/stop-working-all-those-hours.html</url></story><parent_chain><item><author>dsr_</author><text>The article is aimed at the wrong people. Corporate culture starts at the top. Stop judging your employees by the hours they appear, and judge them on results. If you can&apos;t measure results, you were in trouble already.</text></item></parent_chain><comment><author>wilhow</author><text>I agree. Most of the people who works that kind of hours already know and agree with the article. This article should&apos;ve been directed at the managers who require that kind of hours from the employes.</text></comment>