This is bad management practice : Edwards Deming Management Guru (who taught Japanese after WWII Quality and Productivity Management) say that Management by Fear is counterproductive as people will try to cheat the system instead of concentrating on their job ;)
I think in the future this is going to be a mounting risk to be widespread so developers beware...
Though I understand companies want to do so because there are employees who would be lazy there should be better ways, I am thinking about them.
Yes, that's why agree with time tracking apps if they actually just track the time spent. If in 4 hours there are no commits or actual results to represent the time spent "working", that would be an indicator of unproductivity.
I would immediately try looking for an other opportuinity but my salary doesn't allow me to take a time off for now. We'll see how it will go.
I would also try to confront my manager/CTO with the issue, but I'm afraid they'll just think I'm the "lazy employee" who wants to waste time on job time.
don't bother confronting your manager, if they're already this far down the rabbit hole, they'll undoubtedly just hear whatever they want to hear. All you're going to accomplish is increasing your blood pressure.
Tracking work time doesn't really make much sense in programming as it's generally a result obligation. So you don't want to track work-time, you want to track jobs done.
A good analogy is if you bring your car in for repair, and he says it'll be done by tomorrow and cost 200$, so you're paying to get your car repaired by tomorrow for 200$ and he must deliver on that, whether it takes him 5 minutes and he slacks off all the rest of the time or whether he spends all-night repairing your car, you don't care as long as he delivers on what was promised.
I'm a father of four. I started out as a self-taught programmer, completed a B.S. in Computer Science and am currently employed full-time since 1998.
I also own a small mobile software company.
I personally don't like commits being used as a metric. Right now, my team is working on a fairly large project and frequently, we don't commit until the very end of the day (or maybe even the next day). That's mostly because we're spending a lot of time writing, rewriting and discarding our code. Someone could see that as unproductive, but we're learning a bunch of new technologies as we work.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is bad management practice : Edwards Deming Management Guru (who taught Japanese after WWII Quality and Productivity Management) say that Management by Fear is counterproductive as people will try to cheat the system instead of concentrating on their job ;)
I think in the future this is going to be a mounting risk to be widespread so developers beware...
Though I understand companies want to do so because there are employees who would be lazy there should be better ways, I am thinking about them.
Yes, that's why agree with time tracking apps if they actually just track the time spent. If in 4 hours there are no commits or actual results to represent the time spent "working", that would be an indicator of unproductivity.
I would immediately try looking for an other opportuinity but my salary doesn't allow me to take a time off for now. We'll see how it will go.
I would also try to confront my manager/CTO with the issue, but I'm afraid they'll just think I'm the "lazy employee" who wants to waste time on job time.
don't bother confronting your manager, if they're already this far down the rabbit hole, they'll undoubtedly just hear whatever they want to hear. All you're going to accomplish is increasing your blood pressure.
Tracking work time doesn't really make much sense in programming as it's generally a result obligation. So you don't want to track work-time, you want to track jobs done.
A good analogy is if you bring your car in for repair, and he says it'll be done by tomorrow and cost 200$, so you're paying to get your car repaired by tomorrow for 200$ and he must deliver on that, whether it takes him 5 minutes and he slacks off all the rest of the time or whether he spends all-night repairing your car, you don't care as long as he delivers on what was promised.
I personally don't like commits being used as a metric. Right now, my team is working on a fairly large project and frequently, we don't commit until the very end of the day (or maybe even the next day). That's mostly because we're spending a lot of time writing, rewriting and discarding our code. Someone could see that as unproductive, but we're learning a bunch of new technologies as we work.