[vesak]

When I wrote Mastering Rust, I did most of the work during the only available productive hours of the day: 20-05. Amazing legal narcotics i.e. coffee helped quite a lot.

I wasn't miserable, but that's mostly due to the excitement of progressing.

[chrisco255]

Why is late night programming / writing so darn productive? No distractions?

[vesak]

Well, I have theories. One, it breaks habits. You may have teached yourself over the years to procrastinate during the day, but not during the night.

Two, you know it's painful enough that you'd rather not waste the time doing something stupid and worthless.

Three, it lowers your mental state enough that you'll just drudge on like a robot.

[ghostbrainalpha]

For me its about anxiety, and that ability to drudge on.

Certain parts of my brain fatigue and completely turn off. After an all-nighter my emotional resilience is off the charts the next day.

I think a little slower, but so much more calmly, and logically.

At my startup my co-founders actually requested I pull all-nighters before pitching VC's because the effect was so profound. Public speaking is so easy when you stop caring and treat everything like an item on a checklist instead of a potential catastrophe.

[dsego]

No fomo. Everyone is resting/sleeping.

[crawftv]

In my experience, I think the momentum/flow and thrill helps. Also hacking turns into late-night-hacking as I try to dig myself out of hole. So it ends up being productive by trying to finish something before bed.

[jjtheblunt]

that's my experience for sure.

it's not that we're night owls, but that we need coherent blocks of focus-compatible time, so when the rest of the world sleeps is one heuristic.