Earlier quoted context omitted.
Businesses need to stop caring about if you're on facebook 8 hours a day. If you're getting your work done at the end of the week that's all that really matters. The idea that the business owns your ass for a minimum of precisely 40 hours a week where you must be solely focused on the outcome of the business is both toxic and nonproductive.
I think that would be a great - but we also employ by the hour not by the task which I also think is great. Sometimes I get tickets marked with three story points and think "Ha, let me just push up a quick patch" and other times I discover a dark dark hole at the bottom of assumptions that eats away at days. It's really hard to generally evaluate employees on productivity - especially in CS - and so our compromise is…
And I have, though it's always tempered by two things, namely, A. If the job routinely requires > 40 hours a week, then the job is poorly defined and we need to modify expectations, and B. That if I'm working to the job and not the hours, it doesn't matter if I only put in 30 hours one week, if the work is being done (and, likewise, if THAT is routine, the job is also poorly defined, and I need to ask for more things to do).