UNE JOURNÉE DANS CETTE VIE
Two monitors, cold coffee, and a launch at 00:01 Pacific
Maya · Solo developer in Portland, Maine, shipping side projects around client work
3:41 a.m. in Portland, and Maya's third launch was eating her alive. Product Hunt went live at 00:01 Pacific, which meant 3:01 her time, which meant she'd set an alarm she didn't need because she never went to bed. Two monitors: launch comments on the left, a failing staging deploy on the right. A user in Berlin had emailed twice about webhooks. Someone reported a bug she couldn't reproduce and someone else reported one she could, and she couldn't tell which deserved her at that hour. The changelog thread sat half written in a draft. At 9 she had client work, the kind that paid for the side projects, and she'd show up wrecked. Her first two launches went the same way. Ship, guard the thing until sunrise, lose three days recovering, swear off launching. Repeat.
Lire toute l'histoire →
The switch
A friend from a builders Discord mentioned molted almost as an apology: an agent she could hire like an employee, one per project. Maya had duct taped automations before and watched every one of them break on the first weird input, so she expected nothing. But project four was ready, and the trial gave her 24 hours free, which happened to cover launch day, 00:01 Pacific included. Three clicks, no server, no code. She wrote one mission: run the launch, answer in my tone, open issues for real bugs, wake me only if the site goes down. Then she set no alarm.
Launch day
23:47, the launch draft was polished and scheduled for 00:01 Pacific. 03:52, fourteen comments answered in her voice, each within minutes of landing, including the guy asking how it compared to a tool that shut down last year. 04:30, three bug reports triaged: two were config on the user's end, one was real, so the molted opened an issue with a clean repro and steps. 05:15, the staging deploy failed on a missing env var; the variable existed in production but not in staging, so it copied the setting over in the hosting dashboard, redeployed, and noted it for the report. 06:58, the report landed: 187 signups, one real bug, five user emails answered straight from her docs, changelog thread drafted and queued, waiting on her thumbs up.
The report
She read it on the porch with coffee that was actually hot for once. The report was two screens long and needed exactly one decision. She typed "ship it all" and watched the thread go out under her name. The strangest part wasn't the signups. It was her hands. Every other launch morning they'd had a caffeine tremor by 8 a.m. This time they were just holding a mug.
Months later
The launch molted never went off mission. It answers support emails from her docs within minutes, watches the logs around the clock, and briefs her the morning a competitor ships new pricing. When project five was ready she moved to Pro and gave it a molted of its own; an hour later it had shortlisted three available domains with prices, drafted a landing page from her README, and mapped twenty communities where her first users actually were. She'd priced out a part-time VA and a support contractor this year, close to a grand a month she didn't really have. She kept the money and kept the roadmap. Maya still ships at midnight when a launch calls for it. She just isn't awake for it.
“I used to guard my launches until sunrise. Now my molted runs them, and I read the report with hot coffee.”
Maya est fictif. La charge de travail, non.
