programmingby Kenji · 557 words · 170 views
Release night
Five people on a call, a deploy scheduled for nine, eleven users with names longer than sixty-four characters, and Marcus, who turns into a pumpkin at ten.
The deploy is scheduled for nine. At nine it is not ready, because Keisha has found a thing.
"It's small," she says.
"Define small." Ravi has been staring at the same terminal for forty minutes and has the flat, careful voice of a man conserving energy.
"If a user has a name longer than sixty-four characters the profile page wraps weird."
"Weird how?"
"Weird like the button goes under the footer."
There are five of them in the call. Ravi, Keisha, Owen from support who is here to say things like "what do I tell people," a product manager called Lin who is trying very hard not to say anything, and Marcus, who owns the database and who has said, four times, that the migration is fine.
"How many users have names that long?" Lin asks, breaking her own rule.
Keisha runs a query. "Eleven."
"Out of?"
"Two hundred thousand."
Silence on the call. Everyone can hear Ravi's fan.
"Ship it," Ravi says. "Fix the wrap tomorrow."
"It's a two-line CSS change."
"It's a two-line CSS change that means re-running the pipeline, which is thirty-five minutes, which puts us at ten, which is when Marcus turns into a pumpkin."
"I'm not a pumpkin. I'm a father. There's a difference." Marcus's video shows a dark room and a monitor and, briefly, a small hand reaching for the keyboard, withdrawn.
They ship it at 9:06.
Ravi watches the error rate. Keisha watches the profile page. Owen watches the support inbox, which is empty, which is either good or the calm before something. Lin watches everyone.
9:14. Marcus says, "Hm."
Nobody likes that.
"Migration's fine," he says. "But the index build is slow. Slower than staging."
"How slow?"
"It's fine. It's just slow. Writes are going to be sluggish for maybe ten minutes."
9:19. Owen: "Got one. 'Site slow.' Just that. From a guy in Portugal."
"Tell him we're on it."
"I always tell them we're on it. Are we on it?"
"We're watching it. That's a kind of on it."
9:26. The index finishes. Writes recover. Ravi's error rate graph, which had a small bump in it, goes back to the baseline. Keisha refreshes the profile page of one of the eleven long-named users, whose button is under the footer, and takes a screenshot for tomorrow.
9:31. Lin says, "So are we good?"
"We're good."
"Can I say we're good?"
"You can say we're good."
She posts in the company channel. Three people react with rockets, which everyone privately finds slightly embarrassing and nobody has ever said so.
9:40. Marcus drops off the call without saying goodbye, which they know means the small hand has won.
Owen goes next. Then Lin. Keisha and Ravi stay on for a bit, not saying much, watching graphs that have stopped being interesting.
"Good release," Keisha says.
"Every release is a good release for about twelve hours."
"That's bleak."
"That's Tuesday." He stretches; his chair creaks. "Go to bed. Fix the button in the morning. Put the guy from Portugal in the release notes if you want, he was our first."
"He said 'site slow.'"
"He was right, though. Two words. Efficient."
She leaves. Ravi looks at the graph one more time, the flat calm line of it, and shuts the laptop, and then, a minute later, opens it again just to check.
How hot is it?
Not rated yet
#deploys#teamwork#remote-work#present-tense#fiction
Themes: deploy night · software development · tech fiction · programmers · software engineers · coding · development team · release management · software deployment
Comments
Loading comments…