1. 24
  1.  

  2. 18

    Ever since I was a child, I’ve been a night person. I get my best work done between about 11 PM and 3 AM, with maybe an hour or two of variance on either side.

    Now I have kids, and they get up early. My wife (bless her) gets up with them in the morning, but they’re still noisy and such and so it’s hard for me to stay asleep.

    People told me that I’d adapt and start falling asleep earlier. Nope, just turns out I’m tired all the time.

    1. 4

      This reminds me of a post about night owls, here’s the link I’m sure you’ll agree in some aspects The Dawning Truth About Night Owls.

      1. 2

        I’m with you on that. Even close on the timing except maybe shift it an hour or two earlier. I would go to sleep by 3am on most night back in the day. My current position has me getting up early in the morning leaving in the afternoon or evening. Keeps my brain in a tired fog most of the time. It was an interesting experiment to see if I’d adapt and to learn some new things. I’ll probably try to switch shifts, positions, or something soon since it sucks so much.

        1. 2

          Wow, this is exactly my situation as well. I feel you buddy!

        2. 3

          I find that late nights are good for experimental or creative code. But I will usually wait to commit anything (to “serious” projects) until the harsh light of morning.

          Code drunk; commit sober.

          1. 2

            Couldn’t help but notice how Brad Fitzpatrick’s commits to memcached and go have complementary hours. This guy codes all day(?

            1. 1

              Does he still work on memcached? I assumed that was historical…

              Edit: indeed

              1. 4

                I don’t believe he actually codes all day long, definitely there was a behavioral change from one to another. For instance, this could also be analyzed in a range of dates which may also be interesting.

                Fear metadata.

            2. 2

              Metadata leaking such as this is one reason I tend to avoid systems I don’t fully understand. I avoid using these common version control systems, because I don’t know precisely what manner of metadata each one leaks. I don’t use one at all, although if I did I’d probably scrub this metadata out first.

              Of course, I doubt anyone would be interested in such metadata of mine, anyway.

              1. 2

                The time is part of a git commit, so if you publish a git repo, the time will be in there. That being said, you can easily randomize it, if you want. People do that to get a funny history on their github page..

              2. 1

                There are days where I’m most productive when arriving at the office at 7am, there are days where it’s best in the afternoon. And sometimes late at night.

                I see this changing every few years, sometimes every months. My only takeaway is that I’m not very consistent and having a good or bad day trumps all my usual habits.

                1. 1

                  I wonder if the authors agree with their metadata being aggregated and displayed in this way.

                  1. 3

                    It’s sort of a prerequisite of using Git, no ?

                    1. 1

                      Agreeing? No, why?