Cool information! I've always thought that I am more productive in the morning - but now I'm interested in crunching the numbers to see what it actually looks like. Obviously you can be productive and not make commits to a project, but it would still be fun to know.
At what time of day do famous programmers work?
21–30 of 215 posts
Re: At what time of day do famous programmers work?
#22I'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.
I dislike the apparent inability to label groups of changes with `git stash`, so instead before leaving a branch with in-progress changes I'll commit them all as "WIP". Then, when I return to the branch, I'll check if the previous commit was WIP (`git log -1`), and if so will reset it (`git reset HEAD~1`). It's the best workflow I've discovered for dealing with this problem, and it means that I don't lose my commit h…
git stash save my stuff (deprecated)
git stash push -m "my stuff"
Re: At what time of day do famous programmers work?
#23I'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.
I dislike the apparent inability to label groups of changes with `git stash`, so instead before leaving a branch with in-progress changes I'll commit them all as "WIP". Then, when I return to the branch, I'll check if the previous commit was WIP (`git log -1`), and if so will reset it (`git reset HEAD~1`). It's the best workflow I've discovered for dealing with this problem, and it means that I don't lose my commit h…
Temp branches or tags are probably the "proper" way to stash a history of changes in git. `git stash` is mostly a convenience feature for when you want to quickly clean up your working tree to eg. pull latest changes from a remote.
Re: At what time of day do famous programmers work?
#24There 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?
I think is different for every person. I usually commit often but I'd squash multiple commits into one.
So, my graph isn't exactly going to tell you at what hours I code but at what time I sent pull requests to my coworkers for example.
Re: At what time of day do famous programmers work?
#25It's difficult to draw any conclusion since we don't know their work pattern. If you commit at 12 it probably means you were working between 9 and 12, or between 11 and 12 or maybe it's just yesterday's work ? Who knows.
Re: At what time of day do famous programmers work?
#26Earlier quoted context omitted.
I dislike the apparent inability to label groups of changes with `git stash`, so instead before leaving a branch with in-progress changes I'll commit them all as "WIP". Then, when I return to the branch, I'll check if the previous commit was WIP (`git log -1`), and if so will reset it (`git reset HEAD~1`). It's the best workflow I've discovered for dealing with this problem, and it means that I don't lose my commit h…
git stash save my stuff (deprecated) git stash push -m "my stuff"
What GP wanted was to stash a history of commits, not just the current state of the working tree. `git stash` is fundamentally unable to do that.
Re: At what time of day do famous programmers work?
#27From John Carmack:
> I often worked nights and slept during the day, but I almost always got 8 hours of sleep. There are still 112 hours left in the week!
Re: At what time of day do famous programmers work?
#28I wonder how much this is related to age.
Probably also heavily related to whether you have kids or not. I remember Linus saying that before he had kids he used to work during the night, but he had to stop that so he could drive them to school, etc.
Re: At what time of day do famous programmers work?
#29Re: At what time of day do famous programmers work?
#30The work patterns would be more interesting.
Does Bellard think the whole project through for days and then simply hacks it down in a few hours?
Does one of them use TLA+?
Do they use iterative approaches, where the first few versions are really buggy?