I guess only white male programmers are famous in programming ? Good job further propagating the stereotype.
I already commented on this somewhere else. What's the problem with that? Are you implying female/black programmers are different?
At what time of day do famous programmers work?
91–100 of 215 posts
Re: At what time of day do famous programmers work?
#92I don't get why so many people here are up in arms about commits not actually representing real work or when it was done. The author never stated what he thinks a commit represents and yet so many of you try to find some kind of flaw with his method and ascribe your own meaning to words he never said. Just enjoy this for what it is - a simple histogram for commits in a project.
Re: At what time of day do famous programmers work?
#93I wonder how much this is related to age.
Quite a bit i'd imagine. I used to write lots of code at all hours of the day, 8 hours at work, 6+ hours at home. Then i had kids, and while i still write code 8 hours a day at work, i rarely find the time to write anything in my spare time anymore. Every now and then i have "some project" that i'm working on, but it's mostly in bursts of 2-3 days, followed by 3-5 days of "doing nothing". The 2-3 days are _not_ weeke…
And there are other things that distract us with age. Eg I recently bought a house. Now I’m always coming home to do housework instead of coding. Also burnout can happen from acute events which we are more likely to run into over time. I hit a specific conflict at work and mostly lost the will to work OT for years after that.
Re: At what time of day do famous programmers work?
#94It's unfortunate that the author chose to only include male programmers in the post.
Why is it unfortunate? Or am I missing some sort of implication here? And what about black programmers? Does it matter? If so, why?
Hypothetically the author thought of “epic programmers” and only came up with white males. Women and PoC have given great contributions in our industry and are underrepresented. This could have been an opportunity for the author to learn about some and give them a bit of credit.
Re: At what time of day do famous programmers work?
#95It'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.
I don't know, I commit logical units. Changes that do something. If they're a one liner, that's it. If it's 500 lines, that's it. 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.
I would like to do that at work but the code review and Jira ticket adds to much overhead so we mash stuff together to umbrella commits.
That is probably becouse we use Perforce where you don't do local branches by default.
Re: At what time of day do famous programmers work?
#96Earlier quoted context omitted.
> Strange policy about commits — why just not push at night or during weekends? Why's everyone not working on branches That is what I’m saying. The policy is avoid pushes to master. My policy does apply to branches too once there are more than a few people in the branch. Lots of people do work in branches, but everywhere I’ve worked, plenty of people skip branching when they’re making what they think are “small” chan…
We have emergency production rollback to the last working deploy. That's what you do when breaking changes are committed to master. Letting devs commit to master directly? Horrible idea.
That’s a great strategy that works in some scenarios. Preventing weekend breaks would depend on a daily deploy schedule? I do normally revert first and ask questions later when breaking changes appear, that’s similar to what you’re saying, I think...
> Letting devs commit to master directly? Horrible idea.
I’ve never been on a team that disallows commits to master. I can see the thinking, and maybe I should be doing that, but for whatever reason, the places I’ve been are less formal than that and they might be concerned about slowing down turnaround times during the day when people need to share things more quickly.
FWIW, I am including git and also VCSs other than git. It’s harder to wall off the master branch in Perforce as a policy decision. And maybe I just haven’t been on a large enough team to warrant having someone with full time merge duties...
Re: At what time of day do famous programmers work?
#97Re: At what time of day do famous programmers work?
#98Earlier quoted context omitted.
Strange policy about commits — why just not push at night or during weekends? Why's everyone not working on branches?
> Strange policy about commits — why just not push at night or during weekends? Why's everyone not working on branches That is what I’m saying. The policy is avoid pushes to master. My policy does apply to branches too once there are more than a few people in the branch. Lots of people do work in branches, but everywhere I’ve worked, plenty of people skip branching when they’re making what they think are “small” chan…
I think the reason for confusion is that you seem to say that people doesn't even commit their work when they work, but only when they're pushing as well. dchest is (seemingly) asking why don't you commit when you're done, but delay the pushing (according to your policies)?
Re: At what time of day do famous programmers work?
#99I 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…
The one for Chris Lattner is definitely off: https://twitter.com/clattner_llvm/status/1150992062365310977
Re: At what time of day do famous programmers work?
#100I 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.
This is a good example of the ages old falsehoods about time. You're mostly right, but you're missing leap seconds.