Building & Shipping

Two Production Fixes From the Back Seat of a Car

Brett Ridenour Brett Ridenour · Published July 2026

Freebo has a real operator on it now. A small boat-charter shop, taking real bookings from real customers on my platform. Which means production problems are not mine to sit on anymore. They are someone’s Saturday.

Two showed up at once: the reschedule flow needed a fix, and a card charge was not behaving. Normally that sentence ends with “so I drove home and opened my laptop.” This time I was in the back seat of a car, somewhere in the mountains, nowhere near a desk.

I fixed it by talking

I have a voice-driven task agent I call ARIA. It runs the same tools I use at my machine. I just talk to it. So I did.

“Fix the reschedule flow and launch it.” Done in under a minute. “Fix the card charge.” Done in about fifteen. Two production issues on a live payments platform, resolved before we were out of the canyon, without me ever unlocking a keyboard.

The gap that closed

For most of the time I have been building, the distance between noticing a production bug and shipping the fix was physical. Get to a laptop. Open the repo. Find the file. That distance is why small problems sat for hours.

Now the distance is a sentence. I can be a passenger on a road trip and still keep a live platform healthy for the one operator trusting it with their bookings this weekend. That is not a flex about working on vacation. It is the opposite of stress. The thing that used to require me to stop my whole day now fits in the pause between two songs.

Being small and being everywhere are not opposites anymore.