| ▲ | doorpheus 10 hours ago | ||||||||||||||||||||||||||||||||||||||||||||||
Its not that hard to get right. I'm a software dev working in Vancouver and our team was able to track all our timezone dependencies and account for the new offset. The Microsoft team definitely has some organizational issues since they've had 7ish months to fix this. | |||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | rjrjrjrj 8 hours ago | parent | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||
Describing it simply as "the new offset" seems like an oversimplification. Just in BC there were multiple changes, some of which (eg Eastern Kootenays) were decided much more recently than 7 months ago. The MSTNO area didn't change, but in not changing its offset relative to the rest of the province did. Displaying historical data, ranges that include the moment that the new definitions come into effect, temporal and/or spatial aggregations that span multiple timezone definitions... lots of tricky things can pop up. That's not to excuse Microsoft. This isn't the first timezone change that has happened, and they should have the most robust change management process in the world for stuff like this. | |||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | incrudible 10 hours ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||||||||||||||
[flagged] | |||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||