Re:How Not to Do Time Tracking for Software Developers
by zdragnar on Tuesday February 19, 2019 @02:00PM
(#19201726)
I hate to use the "you should be looking harder" trope, but every company I've worked at has had developers at or over 53, and not one of them had such onerous time tracking requirements.
One tracked time to attempt to get r&d tax credits on certain work. The other was an agency that tracked time in case of disputes with unruly clients (such as the time we had gone through 3 project managers and 2 CFOs while we worked with them, and they were desperate to recover money from their own bad mistakes). The rest didn't track time at all.
Not to mention that LOC as a metric has been an industry joke at least since the early 80's: http://www.folklore.org/StoryView.py?story=Negative_2000_Lin... I've heard of funnier versions of that story, but haven't tracked them down yet.
Re:How Not to Do Time Tracking for Software Developers
by lostlogin on Tuesday February 19, 2019 @02:26PM
(#19201938)
LOC means ‘loss of consciousness’ in my industry, but I do t think that fits. What is it here?
Re:How Not to Do Time Tracking for Software Developers
by jki275 on Tuesday February 19, 2019 @02:34PM
(#19201995)
Lines Of Code.
Re:How Not to Do Time Tracking for Software Developers
by 52-6F-62 on Tuesday February 19, 2019 @02:21PM
(#19201895)
That model doesn't even make sense to me.
Some of the most productive hours are LOC removed.
Counting keystrokes?
That sounds nightmarish, man.
In fact, I had to log X keystrokes and Y LOC every hour in order to be paid for that hour...talk about being a factory worker.