[welshwelsh]

>I'd never hire a full time employee who can work remotely. I'd employ a contractor who has to itemize their invoice.

That's not going to save you any money though.

A FT developer who makes $75 an hour only accepts that pay because it's closer to $300/hr in practice (if you only count the hours they are actually productive, which maxes out at 2-3 per day for knowledge work).

A freelance developer of similar skill, who accurately bills per hour worked, will simply charge $300 per hour.

[CountDrewku]

Yeah I don't understand this mentality. You're paying for finished work not hours. People cannot seem to separate themselves from the hourly concept. If you want finished work faster then who cares about the hours?

All you're doing by requiring a certain amount of hours is ensuring the employee stretches out the time it takes to get things done.

[taneq]

> (if you only count the hours they are actually productive, which maxes out at 2-3 per day for knowledge work).

What's "productive", though? Typing at a keyboard? For creative knowledge work (like designing stuff, not answering technical email queries) sometimes the back of your mind just needs time to chew on something.

[throwaway39203]

Time spent tethered to the computer or in the office looking busy isn't as valuable as real free time though, assuming this fully efficient job market a given dev might take $300 for real work + busywork or $250 for just the actual work