5 ms·
I've never understood required hours. Because sometimes 20 hrs in a week is a lot. Other times 60 is no time at all. Those weeks where 20 are a lot I am extreme
by godelski 9y ago
I've never understood required hours. Because sometimes 20 hrs in a week is a lot. Other times 60 is no time at all. Those weeks where 20 are a lot I am extremely distracted and the next day I am not excited for work. The weeks where 60 is no time, most of that is productive and I want to go to work. Judging work by number of hours just seems like a poor metric.
- avinash180 9y agoyes, a poor metric but a measurable, quantifiable metric common to all regardless of their individual capacities in a given time.
- godelski 9y agoI don't believe this. Because your managers generally know who is a good worker and who isn't. The rest of the workers definitely know.
- gerbilly 9y ago>I've never understood required hours. They want you there to answer questions. Workplaces value availability because it's too difficult to design coherent systems and to document them. Instead of that boring old stuff, in the modern workplace, we go fast and break things (or never get them fully working in the first place). Then we expect workers to be always around so they can be reached on slack when there is a problem.
- godelski 9y agoYeah, but with modern technology everyone is almost always reachable.
- SketchySeaBeast 9y agoMore than half of my work is time and materials work (as opposed to a fix bid project), and so it's directly billed to the client. My putting in hours is directly proportional to how much the company makes. I don't like it either, and I feel like I could contribute a lot more effectively on the fixed price items if I wasn't constantly scrounging up T&M work, maybe I'd even have time to think up decent solutions instead of justifying why I have to spend another 2 hours on issue #blah, but it's an example of why required hours exist.