LongitudeEveryone who has worked across time zones has missed a call by exactly one hour. It is almost never a failure of arithmetic. It is a failure of an assumption that was never examined.
Here are the assumptions that break, and the habits that survive them.
Daylight saving is not synchronized, and that is the whole problem
The United States and Europe both shift their clocks. They do not shift them on the same day.
For roughly three weeks in March, and one in late October, London is four hours ahead of New York rather than the usual five. If you scheduled a recurring call during a period when the gap was five hours, and you calculated it once, you will miss one.
The southern hemisphere goes the other way entirely. When New York springs forward, Sydney is falling back. The gap between them changes by two hours, twice a year, in opposite directions.
The habit: never store a time difference. Store a place.
"UTC+5" is a fact about a moment, not about a country
An offset is what a clock reads at a specific instant. A time zone is a rule about how offsets change over the year.
India is UTC+5:30, always, and always will be. Germany is UTC+1 in winter and UTC+2 in summer, and both are correct depending on when you ask.
If you write "the call is at 14:00 UTC+1," you have written something that is true today and possibly wrong in April.
The habit: say "14:00 Berlin time." A city name carries its own rules. An offset does not.
Half hour and quarter hour zones are real
India is thirty minutes off the hour. So are parts of Australia, and Newfoundland. Nepal is UTC+5:45, forty five minutes off, which exists to be exactly fifteen minutes ahead of India for reasons of national self definition.
Nothing about this is a mistake, and software that assumes whole hour offsets is simply wrong. So is a person who does mental arithmetic in whole hours.
Countries change their minds
Time zone rules are political, not astronomical. Governments alter them, sometimes with weeks of notice. Countries have skipped a day entirely to change which side of the international date line they sit on.
Any hardcoded time zone table is a decaying asset. This is why operating systems ship updates to their time zone database several times a year.
The habit: trust your device, not your memory. Your phone updates the database. Your recollection of "Chile is four hours ahead" does not.
The rules that survive
1. Always name a city, never an offset. "9am New York" is unambiguous forever. "9am EST" is wrong for eight months of the year, because for eight months it is EDT.
2. Let the calendar do the conversion. Enter the event in the organizer's zone and let every attendee's device render it locally. Do not send a table of converted times in the invitation body. The table will be wrong in March and nobody will notice until the call.
3. Confirm the day, not just the hour. If you are more than eight hours apart, "Tuesday morning" for you is Monday night or Tuesday evening for them. The hour is usually right and the day is what gets missed.
4. Check the week before it happens. The one manual check worth doing: two days before any important cross zone call scheduled more than a month ago, look at what your calendar now says. If a clock changed in either country, this is when you find out.
5. For anything recurring, pick a zone and say so. "Weekly, 15:00 London" means the New York time drifts twice a year. That is fine, as long as everyone knows which end drifts.
Why a world clock still earns its place
Calendars convert. They do not give you intuition.
Knowing that it is 4am for the person you are about to email is different from knowing what their local time will be at your 11am. The first stops you doing something rude. The second gets a meeting scheduled.
Longitude exists for that first thing: a glance, not a calculation. It works offline, holds no account, and collects nothing about you.
Longitude is a world clock. Zero ads, zero tracking, zero data collection. We literally cannot see your data.