3 ms·
I'm a programmer. I also sometimes manage others. Time tracking and continuous code code review is an important way to spot workers who can't stay on task or a
by kardianos 8y ago
I'm a programmer.
I also sometimes manage others.
Time tracking and continuous code code review is an important way to spot workers who can't stay on task or are way over their head. If you can catch issues early, you can help them and the team succeed. If you lack time tracking and continuous code review many developers will "fall through the cracks" and it will take much longer to discover they are a net negative to the team. Even if it becomes apparent, it becomes much easier to point to sometime somewhat objective then gut feelings.
Time tracking is good for accountability. Time tracking should be simple. Time tracking should only loosely be associated with tasks.
* Email 0:45
* Meet with customer 1:00
* Program Complete solution and deploy it (TASK045) 0:05
I would be very wary of developers who refuse to accurately track their time.
- wolco 8y agoTracking at the microlevel is horrible. The time wasted keeping up and the padding in explainable areas to offset the undocumented task like pick up phone, talk to coworker, get water, go to bathroom, answer question. In your example email took 15 minutes in reality it took 1 minute and I've used 14 minutes to get a coffee speak to an employee about upcoming company bake sale, holding the door for the CEO and getting to the conference room 5 minutes early to meet the client.