3 ms·
Hours are a really terrible proxy for efficiency and effectiveness. If an employee is meeting or exceeding standards they were hired for, the hours are not even
by 0xy 5y ago
Hours are a really terrible proxy for efficiency and effectiveness. If an employee is meeting or exceeding standards they were hired for, the hours are not even a consideration.
The creatives I have working for me on a side project bill hourly, but I'm never checking or adding up whether they actually work those hours. I can see tangible work being done to an excellent standard. That's all that matters.
Paying for time is disrespectful. I'm paying for results. This matches other trades within the community. I'm not paying a baker for 10 minutes of his time, I'm paying him 5 bucks for a loaf of bread (the result of his labor).
If I could pay programmers per loaf of bread produced, I would. But there is no "loaf of bread" metric available. All programming productivity metrics are flawed.
- mooreds 5y ago> Hours are a really terrible proxy for efficiency and effectiveness. I wish I could upvote this 10 times. Unfortunately this is also true: > All programming productivity metrics are flawed. so folks have to arrive at something. You've arrived at: > tangible work being done to an excellent standard Which is a great place, and one where most folks who do 'side projects' or contracting land. (Side note: one of the things I loved about contracting is the matter of fact way most fellow contractors talked about rates and money, with none of the taboo there often is with full time employment.) Employees with full time employment, I submit, have different norms of measuring success. Hours worked often, deliverables sometimes.