the day I quit fixing it
There's a version of this site that never shipped. It lived on my laptop for weeks, perfect, behind a build step nobody else could run. I kept it there because I could.
May 19. Tuesday. I was fixing a hover state.
A hover state. The little color shift when your cursor crosses a link. I'd been at it twenty minutes, nudging a hex value two shades and back, two shades and back. And somewhere in there the truth walked up behind me and tapped my shoulder. Nobody has ever decided not to read something because the hover was off by two shades. Nobody. I was hiding inside the small fix because the small fix is safe. You can always find one more.
That's the trap. The work is never done, so "done" becomes whatever you say it is, and a coward gets to say it never. I'd been a coward for about three weeks.
So I closed the file with the hover state still wrong. Left it wrong on purpose, a little scar to remember the day by. Opened the terminal. Typed the command. The one that takes the folder on my machine and throws it onto the box, the whole press and signal and storefront, the box that costs less than the lunch I didn't eat that afternoon.
I didn't stage it. Staging is for people who want to look at it one more time. I'd looked at it nine hundred times. I ran the real one. Promote.
The thing about a deploy is how fast it is versus how long you stalled to get there. Three weeks of flinching. Four seconds of rsync. The terminal scrolls, files fly by, and then there's a prompt blinking at you like nothing happened, like you didn't just walk out of the building and pull the door shut behind you.
I opened the public URL on my phone, on the cell network, off my own WiFi, because I needed to see it the way a stranger would. There it was. Loading from the box, not my laptop. Real. Ugly in two places I knew about and probably six I didn't. Live.
I sat in the truck in the driveway and looked at it. Quiet for a while.
Here's what twenty years of fixing things in the dark taught me wrong: that the goal is the perfect object. It isn't. The goal is the thing being out where it can hit somebody. A flawless site nobody can reach is a daydream with good production values. A rough one on the open internet is a press. I'd rather own a press with a crooked letter than rent a daydream.
Nothing exploded. That's the anticlimax they don't warn you about. You brace for the platform to punish you and instead the world just keeps not noticing, the way it always was, except now there's a door in it with my name over the frame.
The hover state? Fixed it three days later, from the live site, in about a minute. Turns out you can repair the ship while it's sailing. You just can't launch one you refuse to let leave the dock.
I shipped it broken. It got better in public, where the fixing actually counts.