Hmm. As a software developer you get really frustrated when you have to deal with this expensive piece of software.
Hmm. As a software developer you get really frustrated when you have to deal with this expensive piece of software.
Blessedly, it was an internal tool rather than a way to track client billing; the standing instructions were to just choose some random block of hours corresponding to your total time worked, so that you could get to the project-hours fields that actually mattered. But internal usage also raised the question of why they were voluntarily keeping a tool slightly less effective than a century-old punchclock.
One of my reports worked 4 days a week ... so if they took a half day of leave at any point come the end of the year they would typically have 0.499. or 0.999. left to take.
>if we don't report whole number cap-ex hours on our return, we'll avoid an audit!
When the hours of the tasks didn't add up with the daily attendance you had to tweak your data or you couldn't close the day. Either added or removed 1 minute to the work day.
So a work day with 8 hours maybe had 7.98 hours of tasks. You tweak around a bit so that they both matched.
This was a reported bug (incl. explanation from a programmer) that wasn't fixed for a very long time. Maybe it's still broken.