Late-night deployments used to be a regular part of my work. Here’s what changed — and why my website launches now happen during the day.
Dec 25, 2025
The Late Nights I Don’t Miss
On Monday I was at a pottery class.
Our instructor mentioned she’s retired now. She used to work in software. When I told her I do too, she smiled and said:
“Lots of late nights when you work in software, right? I don’t miss that.”
That single sentence brought back a flood of memories.
In a previous role — long before I started Consumer Mesh — late nights were simply part of the job. At least once a month, we’d plan a deployment that required the entire team to be on a call well into the night.
If everything went smoothly, we were done by 2am.
If it didn’t, well, I’ve been on deployment calls that dragged on until 5am… 6am… even 7am.
Everyone exhausted. Cold coffee. High stakes. And the unspoken understanding that this was just “how it worked.”
At the time, it felt normal. Looking back, it was brutal.
Fast forward to today
Today, I pushed a major update live for a client.
Not a minor tweak — real changes. One of them was upgrading their front-end codebase to the latest version of Next.js.
And I did it:
- During normal business hours
- With zero downtime
- Without a late-night deployment call
Once the backend builds and the content management updates are complete, all I need to do is add any new required content, trigger a front-end build, and thoroughly test the site.
When the build finishes, the update is live.
- No midnight calls.
- No “everyone stay on just in case.”
- No crossing fingers at 3am.
What changed
All of this was generated directly from the client’s design — straight from their Figma file.
- No developer handoffs.
- No translation between design intent and production code.
- No last-minute surprises.
This is how we work at Consumer Mesh.
When I told my pottery instructor that my life used to look like that — but doesn’t anymore — I realized how grateful I am for the shift.
As I’m waiting for a front-end build to finish in the middle of the afternoon, I’m writing this post instead of staring at a deployment clock late at night.
Shipping software doesn’t have to mean sacrificing sleep, weekends, or sanity.
And if you’ve lived through those late-night deployments before, you know exactly why I don’t miss them.
Late-night deployments used to be a regular part of my work. Here’s what changed — and why my website launches now happen during the day.
Dec 25, 2025
The Late Nights I Don’t Miss
On Monday I was at a pottery class.
Our instructor mentioned she’s retired now. She used to work in software. When I told her I do too, she smiled and said:
“Lots of late nights when you work in software, right? I don’t miss that.”
That single sentence brought back a flood of memories.
In a previous role — long before I started Consumer Mesh — late nights were simply part of the job. At least once a month, we’d plan a deployment that required the entire team to be on a call well into the night.
If everything went smoothly, we were done by 2am.
If it didn’t, well, I’ve been on deployment calls that dragged on until 5am… 6am… even 7am.
Everyone exhausted. Cold coffee. High stakes. And the unspoken understanding that this was just “how it worked.”
At the time, it felt normal. Looking back, it was brutal.
Fast forward to today
Today, I pushed a major update live for a client.
Not a minor tweak — real changes. One of them was upgrading their front-end codebase to the latest version of Next.js.
And I did it:
- During normal business hours
- With zero downtime
- Without a late-night deployment call
Once the backend builds and the content management updates are complete, all I need to do is add any new required content, trigger a front-end build, and thoroughly test the site.
When the build finishes, the update is live.
- No midnight calls.
- No “everyone stay on just in case.”
- No crossing fingers at 3am.
What changed
All of this was generated directly from the client’s design — straight from their Figma file.
- No developer handoffs.
- No translation between design intent and production code.
- No last-minute surprises.
This is how we work at Consumer Mesh.
When I told my pottery instructor that my life used to look like that — but doesn’t anymore — I realized how grateful I am for the shift.
As I’m waiting for a front-end build to finish in the middle of the afternoon, I’m writing this post instead of staring at a deployment clock late at night.
Shipping software doesn’t have to mean sacrificing sleep, weekends, or sanity.
And if you’ve lived through those late-night deployments before, you know exactly why I don’t miss them.
Late-night deployments used to be a regular part of my work. Here’s what changed — and why my website launches now happen during the day.
Dec 25, 2025
The Late Nights I Don’t Miss
On Monday I was at a pottery class.
Our instructor mentioned she’s retired now. She used to work in software. When I told her I do too, she smiled and said:
“Lots of late nights when you work in software, right? I don’t miss that.”
That single sentence brought back a flood of memories.
In a previous role — long before I started Consumer Mesh — late nights were simply part of the job. At least once a month, we’d plan a deployment that required the entire team to be on a call well into the night.
If everything went smoothly, we were done by 2am.
If it didn’t, well, I’ve been on deployment calls that dragged on until 5am… 6am… even 7am.
Everyone exhausted. Cold coffee. High stakes. And the unspoken understanding that this was just “how it worked.”
At the time, it felt normal. Looking back, it was brutal.
Fast forward to today
Today, I pushed a major update live for a client.
Not a minor tweak — real changes. One of them was upgrading their front-end codebase to the latest version of Next.js.
And I did it:
- During normal business hours
- With zero downtime
- Without a late-night deployment call
Once the backend builds and the content management updates are complete, all I need to do is add any new required content, trigger a front-end build, and thoroughly test the site.
When the build finishes, the update is live.
- No midnight calls.
- No “everyone stay on just in case.”
- No crossing fingers at 3am.
What changed
All of this was generated directly from the client’s design — straight from their Figma file.
- No developer handoffs.
- No translation between design intent and production code.
- No last-minute surprises.
This is how we work at Consumer Mesh.
When I told my pottery instructor that my life used to look like that — but doesn’t anymore — I realized how grateful I am for the shift.
As I’m waiting for a front-end build to finish in the middle of the afternoon, I’m writing this post instead of staring at a deployment clock late at night.
Shipping software doesn’t have to mean sacrificing sleep, weekends, or sanity.
And if you’ve lived through those late-night deployments before, you know exactly why I don’t miss them.