3 ms·

> 12 years, 5 months at Google > many Google-internal CLs ("change lists" == commits == PRs) > 3,064 Android CLs > 10,787 Go CLs This is at least an average

by fyp 7y ago

> 12 years, 5 months at Google > many Google-internal CLs ("change lists" == commits == PRs) > 3,064 Android CLs > 10,787 Go CLs This is at least an average of 3 commits a day (4 if he didn't work weekends). How is that possible?

mtnGoat 7y ago
Three plus per working day is not terribly hard, you just have to make smaller, more focused commits and be productive. Github claims I have 3,135 in 2017, 2,361 in 2018 and 1,855 in 2019. 7,351 in 3 years.
asdkhadsj 7y ago
Commit count can vary a lot, perhaps? I know I commit far more than my coworkers, but that does not reflect the LOC or "amount" of work. I just visualize and chunk things up into commits more frequently.
- holtalanm 7y ago
  my commit count is really low. i usually squash my commits before submitting a PR. that was the workflow at my previous place of work, so it just became my workflow habitually.
  - google234123 7y ago
    This is not good practice in many circumstances. Large commits are very hard for others to review.
hanwenn 7y ago
I supplied the 3,064 number. In Android, some of the changes get propagated to different branches by an automatic process. It's very much possible that the real number is lower by 10x or so (I didn't check)
scbrg 7y ago
Why wouldn't it be? Just checked my own commit count at work. Averaging 4 daily (including weekends and holidays), in our main repo for the past six years. There's some work going on outside the main repo, if I could be bothered to check all those minor repos the number might bump to ~5. I'm certainly not exceptionally productive or skilled or anything - I just try to make my commits as small as possible. Commit early, commit often.
shurcooL 7y ago
All of the Go commits are public, you can look at them for yourself: • https://github.com/golang/go/graphs/contributors https://github.com/golang/go/graphs/contributors • https://github.com/golang/build/graphs/contributors https://github.com/golang/build/graphs/contributors Brad also once gave a lightning talk about HTTP/2 that had 80+ slides in 5 minutes. He’s very fast.

by fyp 7y ago

mtnGoat 7y ago

Three plus per working day is not terribly hard, you just have to make smaller, more focused commits and be productive. Github claims I have 3,135 in 2017, 2,361 in 2018 and 1,855 in 2019. 7,351 in 3 years.

asdkhadsj 7y ago

Commit count can vary a lot, perhaps? I know I commit far more than my coworkers, but that does not reflect the LOC or "amount" of work. I just visualize and chunk things up into commits more frequently.

holtalanm 7y ago
my commit count is really low. i usually squash my commits before submitting a PR. that was the workflow at my previous place of work, so it just became my workflow habitually.
- google234123 7y ago
  This is not good practice in many circumstances. Large commits are very hard for others to review.

hanwenn 7y ago

I supplied the 3,064 number. In Android, some of the changes get propagated to different branches by an automatic process. It's very much possible that the real number is lower by 10x or so (I didn't check)

scbrg 7y ago

Why wouldn't it be? Just checked my own commit count at work. Averaging 4 daily (including weekends and holidays), in our main repo for the past six years. There's some work going on outside the main repo, if I could be bothered to check all those minor repos the number might bump to ~5. I'm certainly not exceptionally productive or skilled or anything - I just try to make my commits as small as possible. Commit early, commit often.

shurcooL 7y ago

All of the Go commits are public, you can look at them for yourself: • https://github.com/golang/go/graphs/contributors https://github.com/golang/go/graphs/contributors • https://github.com/golang/build/graphs/contributors https://github.com/golang/build/graphs/contributors Brad also once gave a lightning talk about HTTP/2 that had 80+ slides in 5 minutes. He’s very fast.