The build kicked off at 8:51. Standup was at nine. My laptop was sitting on the kitchen counter with the fan running like a small aircraft, and my oldest walked through the background in a towel eating a granola bar, and I thought: not today, not on camera.

So I grabbed my phone, walked out the front door in the hoodie I'd slept in, and stood in the driveway next to the recycling bin I still hadn't rolled back from Tuesday. I dialed into the meeting from there. Eleven degrees cooler outside than in. A neighbor's sprinkler was going. I kept my camera off and said my three sentences — what I did yesterday, what I'm doing today, no blockers — and then I was muted again inside ninety seconds while someone else talked about a ticket I wasn't on.

That was a Tuesday. I know it was a Tuesday because I was still in the hoodie from Monday and the recycling hadn't moved. I stood there in the driveway for the full twenty-two minutes of that standup, phone at my ear, watching the street, waiting for my build to finish on a machine I couldn't see.

How a Driveway Became My Most Reliable Conference Room

Remote work does a thing to you over time where the house stops feeling like a place you go to relax and starts feeling like a place the job also lives. The kitchen is a kitchen until 9 a.m., and then it's a stand-up location with bad lighting. The bedroom is fine until someone schedules a one-on-one at 2 p.m. and the kids get home at 2:15.

I've been doing this long enough that I've taken calls from a lot of places that weren't my desk. I took a whole performance review from a parking lot once, which was its own thing. But the driveway is different from the parking lot. The parking lot is deliberate — you drive somewhere, you make a choice. The driveway is what happens when you just need to get out of the frame and the door is right there.

The build was the proximate cause. I'd pushed a change to a service that had no business being touched on a Tuesday morning, and the pipeline was grinding through it, and the fan noise alone would've killed the audio. Walking outside wasn't a strategy. It was the path of least resistance wearing a hoodie.

Twenty-Two Minutes Next to the Recycling Bin, Camera Off

The standup itself was fine. It's always fine. We go around the call, everybody says their three sentences, and then Marcus talks for six minutes about the infrastructure thing that doesn't affect any of us, and then we're done. I have been on this team long enough to know when I can let my eyes wander and when I need to actually listen, and I spent most of that Tuesday watching a squirrel try to figure out whether the recycling bin was worth investigating.

My camera was off, which I do maybe three times a week and never explain. Nobody has ever asked. I think the implicit rule on distributed teams is that camera-off is its own category of fine, as long as your audio is clean and you say your sentences when it's your turn. My audio was clean. The sprinkler stopped. I said my sentences.

What I didn't say was that I was standing in my driveway, that my laptop was inside running a build I couldn't monitor, and that I had approximately zero idea whether the build was going to pass or fail. I found out four minutes after the call ended. It failed. Wrong environment variable. The kind of thing you catch in thirty seconds if you're looking at the screen, which I was not, because I was outside watching a squirrel.

"Did you just fix it or are you still fixing it?" — my teammate Darnell, on Slack, at 9:24 a.m., with a patience I did not deserve.

I was still fixing it. It took another forty minutes. The standup-to-actual-work gap is real and I keep underestimating it, especially on the days I start the morning doing something I shouldn't have touched.

An Environment Variable, Forty Minutes, and Some Dignity I Wasn't Using

The build failure was on me in the most direct way possible. I'd copied a config from a staging branch without checking the environment key, which is the kind of thing a junior dev does in month two, and I did it on a Tuesday in year several of this job. I've been at this long enough to know better, which made the Slack message from Darnell land a little heavier than it should have.

The fix was not complicated. It was embarrassing in its simplicity. I updated one line, pushed again, waited another eleven minutes for the pipeline, and this time it passed. Total time between "I will quickly push this change" and "the change is actually in" was about an hour and fifteen minutes, most of which I spent either outside near the recycling bin or staring at a progress bar.

The driveway call itself cost me nothing except the build problem I'd already created before I walked out. But I want to be honest about the sequence: I went outside to escape the chaos in the house, missed the failure notification because I wasn't at my desk, and then had to explain to Darnell why a one-line config fix was a forty-minute ticket. That's the actual ledger entry for the morning.

I'm not sure what the lesson is there. I genuinely don't know if staying inside would have made me catch the failure faster, or if I would've just been watching the same progress bar at the kitchen counter with my oldest still in the background eating granola. Probably the latter.

What I Actually Kept From the Driveway Standup Habit

Here's the weird thing: I've kept doing it. Not every day, not even most days, but when the house is loud and the meeting is one where I just have to be present and not actively contributing, I'll grab the phone and go stand outside. It's not a system. I don't have a checklist. It's just that the driveway is quiet in a way the kitchen isn't at 9 a.m., and quiet is worth a lot when you're trying to sound like a person who has things under control.

I also started being more careful about what I push before a standup. Not because I read something about developer workflows or watched a video — I have spent enough time watching people explain their productivity frameworks to know that the advice is always less useful than the embarrassment that precedes it. The environment variable thing was the advice. I just got it the hard way.

Camera off stays. I'm not negotiating on that. On a distributed team where half the people are in different time zones and the other half are clearly in their cars, camera-off is a human right and I will die on that hill from my driveway.

What I dropped: the idea that stepping outside to take a call is somehow a workaround for a bad situation. Sometimes it's just the right call. The recycling bin is still out there. The squirrel situation remains unresolved. The job is still the thing everything else runs on top of, and some mornings the job runs from the driveway in a hoodie, and that's fine.

The recycling bin is still by the curb. I keep meaning to roll it back. I think at this point it might just live there.

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.