Live data from Hacker News

At what time of day do famous programmers work?

ivan.bessarabov.com

211–215 of 215 posts

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

#211
post #210

Earlier quoted context omitted.

Full disclosure: I am definitely not famous, but might be considered a programmer. I found that when hacking for a several months on a solo prototype project, my hours drifted later and later so that I ended up going to bed around 4 a.m., and rising at 11. It's really hard to correct! In terms of productivity, though, the wee small hours are hard to beat.

I'm also certainly not famous -- but I've found the same for myself. I'm far more productive between midnight and 4 or so than any other time of the day. Very hard to make those hours work with a family though.

This has a name: https://en.wikipedia.org/wiki/Night_owl_(person)

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

#212
post #125

Earlier quoted context omitted.

> You can’t count on commit times to demonstrate anything. Very extreme stance! Especially for so deep in thread. Sometimes it’s nice to make your ideas more specific as you go deeper in conversation, not just radicalize and double down.

Interesting; I don’t consider what I said extreme or radical at all. I’ll rephrase it into a question: what do you claim that commit time demonstrates, considering that commit times can and do in practice very often change immediately prior to push?

Commit time has some correlation with when code is written. It’s not perfect, but for me personally it’s usually close.

Whether that correlation models reality closely enough to be useful depends.

My understanding of your “commit time demonstrates nothing” assertion is that you are saying there is no useful information there, which seemed like a radical position for so deep in the thread.

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

#213
post #50

Earlier quoted context omitted.

That's just called a branch. What GP described was committing all their changes into a single WIP commit.

They were describing many different WIP commits, and then later squashing them to a "proper" commit.

That's a branch.

> 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`).

This is a single commit.

Post reply on HN