The case for nocturnal software
We built tools for the harsh light of the open-plan office. The best work happens after midnight — so why does every interface still scream at 4pm?
I spent two weeks last winter rebuilding our editor from the colour up, working only between 1am and dawn in a flat in east London with the overheads off. By the second night something obvious had become undeniable: the software I'd shipped for years was designed for a room I never actually worked in.
Daylight was always the default, never the choice
Every grid, every contrast ratio, every cheerful toast notification assumed a desk under fluorescent tubes at noon. The people who actually live inside these tools — the ones who ship at 3am with one lamp on — were treated as an edge case, a dark-mode afterthought bolted on at the end of a release.
So we stopped apologising for the dark. We rebuilt the whole surface as a club seen through a CRT — black ground, green linework, glow where attention should go and nowhere else. The metrics that mattered, late-session retention and time-to-flow, moved more in six weeks than they had in two years of polish.