Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

At what time of day do famous programmers work?

ivan.bessarabov.com

Post reply on HN
Print view View original

61–70 of 215 posts

Re: At what time of day do famous programmers work?

#61

Post by hmottestad »

I think the calculated wall time incorrectly.

>> The timestamp is the number of seconds since 1st January 1970. If we convert 1563188141 to more human date we'll get "2019-07-15 10:55:41" — that is the time in UTC timezone. Then we add "03" hours and "00" minutes to that time and get "2019-07-15 13:55:41" — that is the time the commit author can see on his wall clock when he did commit.

Usually the +0300 indicates that the times tamp is at +3 hours from UTC. Eg. the timestamp is already in local wall time. The offset can be used to convert it to UTC.

So if the author did what they wrote. Then I reckon all the data is actually in UTC and not local wall time.

Re: At what time of day do famous programmers work?

#63

Post by earthboundkid »

samhh wrote: post #17
wiradikusuma wrote: post #10

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.

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…

You can also use `git commit --amend` to clean up a WIP commit.

Re: At what time of day do famous programmers work?

#64

Post by tuna-piano »

As someone who generally works a 9-5 job at a company where most people are expected to work 9-5, can anyone explain if there are any norms or rules that enable someone to work such abnormal hours at their companies?

Do companies like Google not care as much about work hours? I can't imagine anyone showing up at 2pm at any of the places I've worked, regardless of how productive they were.

Re: At what time of day do famous programmers work?

#65

Post by dahart »

Personally, I’d be very cautious about assuming that commit time has anything to do with work time.

For at least 15 years I’ve had a policy - and so have the people on my teams - to avoid merging or committing to public branches at night or just before & during weekends so that you don’t accidentally hose other people on the team, who rely on automated builds & testing. We write code at all hours, but wait to commit/push/merge to master until the morning when everyone’s there.

I realize that not everyone has policies like that, but these are high profile programmers who are likely to have their own complicating factors. Linus, for example, commits a lot of merges that other people depend on; his code reviews and code writing might be on separate schedules.

Re: At what time of day do famous programmers work?

#66

Post by brianzelip »

holtalanm wrote: post #51
wiradikusuma wrote: post #10

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.

i do this all. the. time. i'll squash multiple in-progress commits into one before submitting a PR.

Do you use `rebase` for that?

Re: At what time of day do famous programmers work?

#67

Post by kawsper »

dahart wrote: post #65

Personally, I’d be very cautious about assuming that commit time has anything to do with work time. For at least 15 years I’ve had a policy - and so have the people on my teams - to avoid merging or committing to public branches at night or just before & during weekends so that you don’t accidentally hose other people on the team, who rely on automated builds & testing. We write code at all hours, but wait to commit/…

Isn't that what feature or topic branches are for? Commit in your own little world, merge when you are ready to share.

Re: At what time of day do famous programmers work?

#68

Post by vomitcuddle »

hmottestad wrote: post #61

I think the calculated wall time incorrectly. >> The timestamp is the number of seconds since 1st January 1970. If we convert 1563188141 to more human date we'll get "2019-07-15 10:55:41" — that is the time in UTC timezone. Then we add "03" hours and "00" minutes to that time and get "2019-07-15 13:55:41" — that is the time the commit author can see on his wall clock when he did commit. Usually the +0300 indicates th…

Unix time is always the number of seconds since 00:00:00 Thursday, 1 January 1970 UTC time. Git records the committer's time zone, since the time would normally be converted back into a human readable form.

Re: At what time of day do famous programmers work?

#69

Post by dchest »

dahart wrote: post #65

Personally, I’d be very cautious about assuming that commit time has anything to do with work time. For at least 15 years I’ve had a policy - and so have the people on my teams - to avoid merging or committing to public branches at night or just before & during weekends so that you don’t accidentally hose other people on the team, who rely on automated builds & testing. We write code at all hours, but wait to commit/…

Strange policy about commits — why just not push at night or during weekends? Why's everyone not working on branches?

Re: At what time of day do famous programmers work?

#70

Post by rurp »

Sharlin wrote: post #23
samhh wrote: post #17

Earlier 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…

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.

I like the approach of creating a new temporary branch for changes I need to stash. When I come back to the work I usually bring the changes back to the branch I'm working in with `git cherry-pick -n `. The -n flag cherry picks the changes over without making a new commit, so I can finish whatever I was doing and then make a proper commit.
Post reply on HN