Midnight Coding Rituals: What Twenty Indie Hackers Actually Drink While Shipping

We asked twenty people who had shipped something they cared about in the last year to tell us what was on their desk while they did it. The answers were weirder than expected, and one pattern we did not anticipate kept appearing.

Cover: A person drinking coffee while working with a laptop
Cover: a generic late-night work scene (stock photo).

The question was small and slightly stupid: "What was on your desk the night you shipped it?" We sent it to twenty indie hackers, solo founders, and one-person SaaS operators in our orbit. Eighteen responded. This post is what they said, lightly organized.

Two caveats before the data. First, this is a survey of people we already know, so it tilts toward a specific cultural profile: mostly North American or European, mostly between 28 and 42, mostly working on B2B SaaS or developer tooling, mostly on their second or third attempt at a solo product. Second, "shipping" here means the moment of actually putting it in front of paying users, not the minor releases that happen every week.

The thing I drank was not coffee. The thing I drank was permission to keep going.

/ 01The headline numbers

Coffee of some kind
13 of 18 (72%). Split roughly evenly between hot and cold.
Tea
6 of 18 (33%). Usually green, occasionally black, once matcha.
Water only
3 of 18 (17%). All three insisted it was "on purpose."
Energy drinks
4 of 18 (22%). Mostly as a supplement, not the main drink.
Alcohol
5 of 18 (28%). Exclusively after the deploy landed.

Numbers add up to more than 100% because many people had multiple drinks across the night. The average shipper reported 2.1 distinct beverages in the six hours around deploy.

/ 02The pattern we didn't expect

Here is the thing that surprised us. We expected the caffeine story to dominate: everyone mainlining espresso, lots of talk about staying up. That is not what we got. What we got, repeatedly, was something closer to ritual.

Thirteen of the eighteen respondents independently described their shipping-night drink in terms that were not about caffeine at all. Sample phrases, lightly paraphrased so as not to identify anyone:

None of these are statements about coffee as fuel. They are statements about coffee as a handrail. Something stable in a night that is otherwise not stable. A way of saying "I am doing the thing" without having to say it out loud.

/ 03Specific rituals, catalogued

A short tour of the stranger ones, with permission.

The Same Four Cups, Every Time #FF5722

One founder, building a billing tool, reported drinking exactly four cups of the same dark roast on every shipping night, in the same rotation of the same four mugs, each numbered in Sharpie on the bottom. He had never articulated this to anyone before. He seemed slightly embarrassed to describe it. We are not mocking him. If anything, we envy the precision.

The Shutdown Beverage #FF5722

Three respondents talked about a specific end-of-shipping drink — not during the deploy, but after. Two reported whiskey; one reported chamomile tea. In all three cases it was described as "the signal that I'm allowed to stop now." Caffeine is a go signal. These were explicitly designed as stop signals.

The Unfinished Cup #FF5722

Four people described drinking only part of their cup. Not because it got cold — because finishing it felt like permission to move on to something else, and they were not ready for that. This is probably the strangest pattern in the data. We have no framework for it. We are including it because it kept showing up.

The Paired Food #FF5722

Six respondents mentioned a food item explicitly paired with their shipping drink — a specific cookie, a specific slice of toast, one case of cold leftover pizza. These were described as "the same thing every time," regardless of how mundane. The food was part of the ritual, not incidental to it.

/ 04What this means, if anything

We think the lesson is smaller than it sounds, but real. The drink on your desk during shipping is not mostly about the chemistry. It is mostly about giving your nervous system a repeatable pattern to cling to during a high-stakes act. Coffee happens to be a good candidate for this role because it involves preparation, temperature, and a physical object you can hold.

Energy drinks, interestingly, did not show up in the ritual descriptions. Nobody said "I crack open a Red Bull and that means I'm shipping." They said "I cracked one when I got tired." Ritual versus tool. Different things.

If you are an indie hacker who feels a little silly about your shipping-night drink routine, here is our official position: it is not silly. It is load-bearing. Keep doing it. And if you do not have one, consider building one. The nights are already hard. Having one thing that is always the same makes them less hard.

/ 05How to build a ritual that actually holds

A ritual is not a recipe. It is a sequence of small, repeatable actions that tells your nervous system what kind of night this is. The people in this survey did not all drink the same thing, and they did not all work the same hours. What they shared was a pattern: the same mug, the same first step, the same drink at the same point in the work. That repetition is the point. When the work is uncertain, the ritual is the one part of the night you can control.

If you want to build one, start smaller than you think. Pick one drink, one vessel, and one moment. It might be a French press started the moment you open your editor, or a pour-over made after you have written down the three things the night must accomplish. Do that same sequence for a week before adding anything else. A ritual that depends on five special items and a perfect kitchen will fail on the first tired night. A ritual that depends on one kettle and one mug will survive.

Environment matters, and it is mostly unglamorous. A clear desk, a glass of water next to the coffee, a light that does not strain your eyes, and a phone in another room will do more for a long session than any new brewer. Water in particular is easy to forget and easy to fix: coffee is not a substitute for hydration, and a headache at 2am is often dehydration wearing a caffeine costume. Keep water within reach, and drink it between cups rather than after you already feel rough.

Finally, a ritual needs an ending as much as a beginning. Several people in this survey had a closing drink or a closing action that marked the end of work, and that boundary mattered. It might be a small cup of tea, a short walk, closing the laptop lid, or writing tomorrow's first task down before you stop. Without an ending, a shipping night can bleed into a sleepless morning, and the next day pays for it. This is not medical advice, and caffeine affects everyone differently. It is simply an observation from people who ship regularly: the nights that end cleanly are easier to repeat than the nights that just dissolve.

// keep reading

More coffee writing in this section — no signup, no preorder, just the journal.

More in Build →
// filed under
indie hacker midnight coding shipping rituals coffee for developers coding coffee late night coding coffee developer lifestyle hexroast