4 ms·

why stop it at 15 minuites? I can't imagine a single scenario where splitting time reported into anything less than hours would matter all that much, and the be

why stop it at 15 minuites? I can't imagine a single scenario where splitting time reported into anything less than hours would matter all that much, and the best possible systems would be more freeform in approach, allowing the worker to specify the actual time they started and stopped, rather than only being able to start and cease work in specific intervals. It would allow for greater resolution naturally where the worker is switching tasks more often. As for people saying such a system would be misused or completed lazily, those arguments apply equally well to filling out timesheets at all. I don't imagine anyone ever recorded themselves slacking off intentionally on a timesheet.

patmcguire 7y ago
It's think it's pretty common when billing for time when the base rate is high. Lots of big law firms bill in six minute increments.
- RugnirViking 7y ago
  but why not just record when you started and stopped each task, rather than dividing the day into chunks needlessly?
  - maximente 7y ago
    you need to convert into billable units at some point, which is what the fractional system gives you, so it's just a matter of whether or not the UI accepts clock based input or not. i'm not a UI expert but timekeeping doesn't seem particularly innovative. there are probably all sorts of esoteric certifications and approvals one might need for e.g. DoD compliance, so i'm guessing there are few people thinking about this and fewer willing to get it done and certified for the sake of the users.
    - codinger 7y ago
      :Cough: selenium :cough: scheduled cronjob
Havoc 7y ago
>why stop it at 15 minuites? It's arbitrary. Everyone from junior to top level does time sheets our side. And accuracy expectations are a little bit malleable in that context. 15 mins has crystalized as a good all round unit of account. I've definitely booked entire days to one code though. And given juniors a hard time about half an hour. It's a very context sensitive thing. Worth pointing out that this is a finance professional firm though not programming...so we might not be speaking the same language here.

patmcguire 7y ago

It's think it's pretty common when billing for time when the base rate is high. Lots of big law firms bill in six minute increments.

RugnirViking 7y ago
but why not just record when you started and stopped each task, rather than dividing the day into chunks needlessly?
- maximente 7y ago
  you need to convert into billable units at some point, which is what the fractional system gives you, so it's just a matter of whether or not the UI accepts clock based input or not. i'm not a UI expert but timekeeping doesn't seem particularly innovative. there are probably all sorts of esoteric certifications and approvals one might need for e.g. DoD compliance, so i'm guessing there are few people thinking about this and fewer willing to get it done and certified for the sake of the users.
  - codinger 7y ago
    :Cough: selenium :cough: scheduled cronjob

Havoc 7y ago

>why stop it at 15 minuites? It's arbitrary. Everyone from junior to top level does time sheets our side. And accuracy expectations are a little bit malleable in that context. 15 mins has crystalized as a good all round unit of account. I've definitely booked entire days to one code though. And given juniors a hard time about half an hour. It's a very context sensitive thing. Worth pointing out that this is a finance professional firm though not programming...so we might not be speaking the same language here.