Why I Build Things at 2am

It is 2am. Lo-fi playlist running. Sprite is open on the desk. Notifications off. And for some reason, this is when the thinking gets clear.

I have been this way for years. Long enough to stop feeling guilty about it and start working with it instead of against it.

The obvious part

The world is quiet at 2am. No WhatsApp messages. No one booking a meeting. No context switching between a client question and a codebase. Your brain gets to stay in one place for more than 20 minutes at a time, which if you have never experienced it as a developer, is genuinely a different cognitive state.

Deep work is not just a book concept. It is a real thing. And for most people with jobs and businesses and responsibilities, deep work during office hours is nearly impossible to protect. The only reliably uninterrupted time I have is when everyone else is asleep.

The less obvious part

There is also something about late nights that lowers the internal critic. During the day, building feels high-stakes. There are standards to meet, people who might see the work, reasons to overthink before committing. At 2am, you just build. You try the thing. You break it and fix it without the weight of an audience.

Some of the best features on UniApplyForMe were built between midnight and 5am. Not because that is a good system, but because that is when the ideas would not leave my head and I had the space to actually follow them.

What the lo-fi actually does

Music with lyrics competes with the part of your brain doing language work: naming variables, writing copy, reading documentation. Instrumental music at a low volume fills the silence without competing. It is background texture. It also signals to my brain that we are in work mode, which after years of conditioning is a real effect.

The Sprite is just preference. I am not going to overclaim that.

The honest tradeoff

I am not romanticising sleep deprivation. Working late and waking up early is not a sustainable strategy. What I have learned is to protect morning energy for output tasks, meetings, and communication, and to use late nights for the creative and problem-solving work that requires unbroken concentration. Not every night. Not as a rule. But when the idea is there and the timing allows, I follow it.

The best commits happen when no one is watching. That has been true every year I have been building.

The work that matters most is usually done in the margins of the day everyone else is not using.

If you are a developer or builder who does the same, I would genuinely like to know. Find me on X or LinkedIn. The 2am crowd is small but committed.