Re:LinkedIn to pay nearly $6M in unpaid overtime wages and d...
by rahimnathwani on Tuesday August 05, 2014 @09:06PM
(#8140427)
Someone should make a tool to calculate working hours from a git commit history and/or bash history.
[ Parent
| on HN ]
Re:LinkedIn to pay nearly $6M in unpaid overtime wages and d...
by groovylick on Tuesday August 05, 2014 @10:11PM
(#8140643)
The amount of time it takes to complete work for a commit is highly variable. I've had commits take a few minutes up to a day's worth of work when debugging something complex. A simple mean time per commit seems like a poor metric.
Re:LinkedIn to pay nearly $6M in unpaid overtime wages and d...
by jpatokal on Tuesday August 05, 2014 @11:46PM
(#8140899)
Sure, but you're obviously working at the point you commit. For example, if my first commit of a day is at 9:15 AM and the last one is at 7 PM, odds are pretty high I've exceeded the 'allowed' 9-to-5 hours.
Re:LinkedIn to pay nearly $6M in unpaid overtime wages and d...
by talmand on Wednesday August 06, 2014 @10:17AM
(#8142556)
1. Commit something at 9:15 AM
2. Go out and enjoy life
3. Commit something at 7 PM
4. Profit!
I'm in.
Re:LinkedIn to pay nearly $6M in unpaid overtime wages and d...
by jboggan on Tuesday August 05, 2014 @10:06PM
(#8140617)
Well, we do a lot of work outside of what our commits show, but that sort of thing would be useful to at least form an estimate. But if you are in the position of the employee claiming that you worked say 50 hours a week for two years, it is the company's responsibility to have your hours accounted for over that whole period. Practically they cannot produce that kind of information and your assertion will probably stand.