News for hackers. Stuff that matters.
Re:Lessons from 2 months of remote working by dinkumthinkum on Monday November 25, 2013 @04:06PM (#6797007)
This applies to traditional work too, doesn't it? Sure, a brick layer can measure based upon how many bricks but I don't think it makes sense for programmers to measure a "good day's work" in terms of just time spent coding ... I think it is more about progress. Even if you didn't write any code, did you make some conceptual breakthroughs that will lead to better coding tomorrow?
Re:Lessons from 2 months of remote working by lukethomas on Monday November 25, 2013 @04:25PM (#6797158)
I understand what you are saying, however, I'm wondering how OP personally measures overall progress as a remote worker.
Re:Lessons from 2 months of remote working by Xeoncross on Monday November 25, 2013 @04:55PM (#6797350)
For me, it's not based on the work, it's based on the mood/mind. A "good day" is one where I was thinking clearly and solving problems and choosing good paths with ease.

The amount of code written doesn't mean as much.

Re:Lessons from 2 months of remote working by AnIrishDuck on Monday November 25, 2013 @07:46PM (#6798266)
In fact, the amount of code written can often be inversely proportional to the quality of your work in that day.

There simply is no meaningful correlation. It usually takes the talent of another skilled professional to measure the quality of your work, which is one of many reasons why management exists.