51–60 of 215 posts
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.
It's interesting to me hearing people in the comments talk about committing after hours of work. I instinctively commit after every maybe 30 loc, especially if I feel it has value. I'll sometimes squash them down if the PR turns out particularly noisy. It would be interesting to compare the average size of commits as well I'd imagine.
If it's more than a day of work I might commit and push unfinished stuff before i stop for the day, but otherwise no.
Edit: although the latter happens very rarely. IMO if a unit is a whole day of work, maybe it needs splitting.
Do all these individuals work from a US time zone, or does fit report the user’s local time zone from which the commit was made?
> The script uses the time the author saw on his wall clock when doing the commit. I can't imagine better time to use for such graphs
[1] https://gist.github.com/bessarabov/674ea13c77fc8128f24b5e3f5...
It's interesting to me hearing people in the comments talk about committing after hours of work. I instinctively commit after every maybe 30 loc, especially if I feel it has value. I'll sometimes squash them down if the PR turns out particularly noisy. It would be interesting to compare the average size of commits as well I'd imagine.
Sometimes it's possible to meet these criteria after writing just 30 lines of code, but more commonly it will take 100-300 lines of code and several hours to get to that state.
It's unfortunate that the author chose to only include male programmers in the post.