11–20 of 215 posts
There is a possible issue though - would they commit immediately after coding - how long do they need to work on a commit before actually committing it?
Another issue is that when you travel to a different timezone, you don't necessarily update the timezone of your system.
Does this take into account timezones?
I wonder how much this is related to age.
There is a possible issue though - would they commit immediately after coding - how long do they need to work on a commit before actually committing it?
Another useful graph would be commit volume versus time (where volume is e.g. number of lines modified)
There is a possible issue though - would they commit immediately after coding - how long do they need to work on a commit before actually committing it?
For one or two isolated commits, that is a fair question. But with hundreds I think it evens out. A more detailed analysis could also take in account the number of changes. How many files per commit? How many lines, maybe? The day of week is also a very interesting metric, that is very visible e.g. on github's timeline. I know my busiest days in terms of commits are in the middle of the week, a marked decrease on Fri…
I'm a forgetful person, so I commit very often but with label "tmp", and later I squash them all into 1 proper commit before pushing. I'm sure I'm not alone, so commit time can't be used as barometer.
Earlier quoted context omitted.
Another issue is that when you travel to a different timezone, you don't necessarily update the timezone of your system.
Aren't most devices configured to adjust automatically these days?
Generally I take a small light laptop when traveling, and then just connect to the desktop back home for doing real work such as committing code.
I know that at a lot of Big Cos do not let their engineers to have source code on laptops anyway (so easily lost and stolen).