|
|
|
|
|
|
by tsotha
4903 days ago
|
|
|
You don't care what the equivalent of 9:00 AM and 5:00 PM are where they live, because that's not actually what you're interested in knowing. You want to know when you can schedule meetings with them. The easy way would be to just keep a list of the other party's available hours in UTC. If you had to deal with a lot of people in a lot of different places, you could keep a list by major city the same way you do with time zones. The fact that you need to apply an "algorithm" to something that's inherently static should tell you the situation as it stands is inefficient. |
|
|
Alternatively, I can just use TimeZones which does it for me, In every country of the world that I've worked with. This even accommodates daylight savings, when people come into work earlier/later at certain times of the year. And my algorithm takes all of 5 seconds per meeting - I wouldn't call it inefficient.
UTC is great for a lot of things (I was one of the people who introduced it to our NOC, ensured that on all servers, /etc/localtime -> /usr/share/zoneinfo/Etc/GMT so our log files could be easily correlated.) - but for figuring out when people around the world are available to work with you - local Time Zones do a much better job.
Also - as noted elsewhere, when I'm traveling from country to country - Having a local timezone to tell me if I'm landing in the morning/afternoon/night is invaluable. Once again - only possible with Local Timezones if you want to represent the time with a single number.