lulzx.comwriting →
← writing

The timezone advantage

sproutApr 20243 min read

I'm in India. Most of my clients are in the US or Europe. People treat the gap as a problem I should apologize for. The gap is the product.

When my American clients go to sleep, I start working. When they wake up, the thing they asked for is done. It feels like magic to them. It's just timezones. Their evening ticket is my morning. Their morning inbox already has a diff.

The same clock that looks awkward on a calendar is a free overnight shift if the work can move without a voice on the line. I get a quiet block. They get a finished thing. Nobody stays up to perform overlap.

The handoff has to be written

The async part is the whole mechanism. I don't do meetings if I can avoid it. Write it down. Put it in a ticket. I'll read it and respond with code. A ticket that names the outcome, the constraint, and how we'll know it's done can sit overnight without losing a word. A "quick call" cannot. Someone is always in their pajamas, or skipping dinner, or half in another meeting.

Meetings across timezones punish both sides. One person stays late. The other wakes early. The recording is worse than the page you could have written in the first place. A well-written message works in every timezone. I've had entire client relationships where we never had a single call. Just messages and pull requests. The work spoke for itself.

The failure mode is a question that only I can answer, sitting in a thread until I wake up, while they sit blocked. I try to leave the next step in the PR before I stop. What I changed. What I did not. What I need from them if the build goes red. If they do the same on their end, I never start a morning by guessing.

Reliability is the overlap

Europe and the US are different clocks, same rule. Europe overlaps my afternoon. The US overlaps almost nothing unless I stay up. I do not rearrange my sleep to pretend we share an office. I rearrange the work so a question I cannot answer is rare. If I need a decision from them, I put the recommendation in the ticket before I stop, the way I would for a team with no meetings at all. They can approve from their morning coffee. I pick it up the next day.

I do not need a two-hour window on the calendar if the last message was enough. When something is actually on fire, we pick a short overlap and we keep it short. The rest of the week runs on the queue. Tickets, comments, green checks. I show up every day and I close what I said I would close. That is the contract. Location is a footnote.

Remote work from here is a written handoff plus a clock that keeps moving after they log off. Do that cleanly and the distance disappears. Do it sloppy and the distance is all anyone can see.