Standup I Took While the Build Ran

The build had been running for eleven minutes when the calendar notification popped. Standup in two. I had one terminal window cycling through a test suite that should have finished before lunch, a second window open on a Slack thread that was aging badly, and a plate of rice and black beans on the desk that I had reheated once already and was about to ruin a second time.

I clicked "Join" anyway. Camera on, mic muted until my name came up, fork in my hand like that was a normal thing to have during an engineering sync. The build percentage sat at 71% in the corner of my screen like it was waiting for applause.

This is the day job. Not the DoorDash, not the surveys, not whatever my brother-in-law texted me about that morning. The actual floor. And some days the floor is a nine-minute standup where you eat cold rice standing up and pretend everything is fine.

How a Slow CI Pipeline Ate My Lunch Break

The build was my fault, which I will admit here and nowhere else. I pushed a change before fully reading a comment thread about a dependency conflict that two other engineers had already sorted out the week before. Classic. I merged anyway because I was watching the clock and convinced myself it would probably be fine.

It was not fine. The pipeline caught it, flagged it, and started a full re-run that would take — according to the progress bar I was now staring at — somewhere between fifteen minutes and geological time. I had already been through a version of this with a build running in the background during a standup outside, and I should have known better. I did know better. I did it anyway.

The lunch I'd made — rice, beans, a little hot sauce, which is my version of cooking — had been sitting there since 12:10. It was now 12:48. The standup was at 1:00, scheduled for fifteen minutes, which in practice means anywhere from nine to thirty-two depending on whether anyone pulls up a screen share.

Nine Minutes of Camera-On, Fork-in-Hand Professionalism

It ran nine minutes, which is the best-case scenario. My update was: blocked on a pipeline re-run, no blockers from anyone else, should have a PR ready by end of day. All of that was true. I said it clearly and without visible panic, which I consider a personal achievement given that 71% had become 74% and then stalled again while I was talking.

Marcus, one of the senior engineers on my team, asked a follow-up about the dependency thing. Not pointed — he genuinely wanted to know if I needed the PR he'd already merged to be re-pulled. I said I'd check. What I meant was: yes, almost certainly, and I should have checked before the standup, and I knew that when I joined the call.

"Just ping me when you're back in it, I'll walk you through the diff."

Marcus is good people. He has never once made me feel dumb for something I should have caught, which is either generous or a very long con. I pinged him at 1:14. He responded in four minutes with a clean explanation. The build finished at 1:22 and came back green. I ate the rest of the rice cold, standing at the desk, reading his message a second time to make sure I actually understood it and wasn't just nodding at my screen.

The Slack thread that had been aging badly resolved itself while I wasn't looking. That happens sometimes. You come back from a standup and two people have just figured it out without you. I find this both relieving and slightly humbling, which is probably the right combination.

Cold Rice, One Hour of Focus, and the Quiet Tax of Multitasking

The rice was fine. I've eaten worse. What it actually cost was closer to an hour of real focus — the kind where you're actually reading the code and not just skimming it because you're half-watching a progress bar. I've written before about what happens when the job bleeds into the margins and the margins close. This was a smaller version of that. No window closed. Nothing was lost. But the afternoon was choppier than it needed to be because I'd started the day by not fully reading a thread.

There's a version of me that would have spent the standup with the camera off, eating hot food, and caught up on the recording later. I've done that. It works fine until it doesn't — until someone asks a direct question and there's a two-second pause while you unmute and swallow. I've had that pause. It's not a career-ending moment. It just feels like one for about four seconds.

The real cost here was the dumb tax I paid for moving fast on a push I wasn't confident about. That cost me Marcus's time, my afternoon momentum, and one plate of rice that deserved better. I don't know what Marcus's time is worth to the company. I know what mine is. I try not to waste either.

What I Actually Changed After Eating Cold Rice at 1:22 PM

I put a sticky note on the monitor that says read the thread. Not because I needed the reminder — I know to read the thread — but because apparently I need the reminder. It's been there for three weeks. I have read it zero times consciously. It might be working subconsciously. I genuinely cannot tell.

The camera-on-during-standup thing I'm keeping. I've tried doing standups from weird locations and the camera thing has never actually been the problem — the problem is always something I did before the call. The call itself is nine minutes. I can handle nine minutes.

What I dropped was the habit of pushing a change right before a scheduled sync just to feel like I'd done something. That's a trap. It feels like momentum and it costs you the actual momentum you need for the afternoon. I've been doing the thing where I look at the calendar before I push anything, which sounds so obvious that I'm a little embarrassed to type it. But it's working. Mostly. I did it again last Thursday but that one resolved cleanly, so I'm not counting it.

I also started eating lunch before noon when I can swing it, which has nothing to do with engineering discipline and everything to do with not wanting to explain to my youngest why there's a plate of cold rice on my desk at 1:30 in the afternoon. That's a harder question than the dependency conflict was. I've thought about what food actually costs when you factor in the time around it, and lunch is part of that math too — I just usually don't count it until it's already cold.

The build is green. The PR merged before five. Marcus got a clean ping and probably forgot about it by dinner. The rice is a loss I've accepted. The day job keeps going, the way it always does — not dramatic, not glamorous, just the thing that has to work so everything else has somewhere to stand.

Note: Everyday Hustle Jeff is the written side of a digital series. These accounts are composite and dramatized. Any figures are what they were on the day, for one person, and are not a projection, a track record, or advice.