yulkes

Silly article. March is when yearly bonuses are distributed, so every year they peak in March and nosedive in April.

>>> The average salary in this sector was ... ($8,634) in April, an 8% increase from last year but a decrease from the all-time high average ... ($9,685) recorded in March.

In Meekan we help schedule meetings based on time ranges, like "9am in the next 3 weeks". We obviously store scheduled event times in UTC. However, that "in the next 3 weeks" day range could change offset in the middle, so we have to keep which timezone we're talking in. As kristiandupont said - timezones are great for future ones.

Also, when presenting times to users, knowing what timezone they're in, helps us display the dates with the correct offsets (without need to change it twice a year).

Timezone codes are useful. They're better in offsets in any way since they contain more data. It's one of those headaches for developers that save headaches to the users.

Hey, not OP, but dev and founder here.

What do you think of the domain? Of the bot approach? Of scheduling meetings in general?

Thanks!