Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

better time reporting may be UNgood for your productivity 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Well, in my case the reporting initially wasn't primarily for tracking people's time (that came later), but for tracking projects' time (and unfortunately, time spent on activities in projects which everyone hopefully ignored and put everything on "development" if that was the main activity that week).

    I'm not sure, but I suspect no one actually used this information for anything useful.

    Let me put it this way. This company, while very competent and cluefull in some ways, signed a seven year contract with Acc

    • Keeping track of worked hours isn’t the most important battle to fight in that situation, epecially when most people around you aren’t unreasonable morons.

      Hear here! If keeping track of employees’ worked hours seems like a solution to anything, it probably means you have bigger problems that won’t be solved by keeping track of employees’ worked hours. I really don’t understand why making the base assumption that your subordinates are shysters ever seems like a good idea to anyone. It would seem to me that merely making this assumption (whether it is grounded in reality or not) should immediately ring mental alarm bells – something has to be seriously amiss if you must operate on this basis.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.