Earlier quoted context omitted.
So here's a question that I continually ask myself as I work at my remote, salaried 6-hour-a-day developer job that I've been doing for the last year: how do I know how much work is enough? If I gauge by productivity, that's cool... I'll just be really fast and get my stuff done and then go play banjo or whatever. But then when folks hand me a crufty WordPress site that is misbehaving and it could be anything between…
Absolutely. I don't fully understand workplace cultures (including my own) that claim to care more about "getting your work done" than "hours in a chair." The problem is that output is in many cases a very crude measure of effort. And not just because some people are vastly more productive than others, but also because it's often the case that when reading a bug report, you don't know if the fix will take 3 or 3000 l…
If a sales guy commit more features to the customers than reasonable, do you need to put in more hours to "getting the work done"? Does he need to stick around late till your are done to penalize him also? If a sales guy doesn't make a sale as aniticipated does he need to stick around until he makes a sale and "gets his work done"?