Why I Like Coding Late at Night

I was chatting with a friend about daily routines the other day, and mentioned that I often find myself coding at 2 AM. The response was a horrified "Aren't you tired?"

Honestly, I can't quite explain it. Coding during the day and coding late at night feel like two completely different experiences.

During the day, there's the constant barrage of messages, meetings, and things demanding instant responses. Your attention gets sliced into fragments. Just as you're entering the flow state, your phone buzzes. By the time you've dealt with the message, that elegant solution you were about to code has evaporated into thin air.

Late at night, it's different. After 11 PM, the world gradually quiets down. The phone stops buzzing, Slack stops pinging, and the only sound outside is the occasional car passing by. That's when I open my editor, put on my headphones, and suddenly the entire world shrinks down to just me and the code.

Some say productivity drops at night, but for me, it's quite the opposite. Those late hours are the only time I can truly focus. Two uninterrupted hours at night get more done than six hours during the day.

Of course, this isn't a healthy habit. Staying up late is bad for your body — everyone knows that. But some things are like that: you know it's not right, yet you can't seem to quit.

Maybe one day I'll fix my sleep schedule and become a "normal person." But until then, I'll keep enjoying those quiet late nights, and the feeling that the whole world is asleep while your screen is the only one still glowing.

If you're also coding late at night, just know — you're not alone.