Today we have something like a mini apocalypse here. Besides the fact that February is already a leap year, they also decided to extend it by an hour, one-time moving the clocks westward. What could go wrong, right?
Everyone as usual just gets confused about which way to move. Someone's time just didn't move on devices, someone's did. People don't understand each other about what time they're agreeing on. But that's expected, okay.
As for technology, there it's naturally unexpected, about like snow in winter for utility services. Roughly speaking, all their life most of the country's services lived and worked on +6 and here suddenly they should work on +5. We mobile devs are simple people, if we didn't do it in advance, it's too late to worry. But backend devs, devops and QA all with matches in their eyes are trying to smooth this transition as they can. Can't hope that in the near future we won't be sorting out random bugs.
By the way, the very idea of moving time on the night of the first day sounds not great, because often vital processes like billing fall on this night.
In addition to this there's no electricity at home and mobile internet works very badly. Coincidence? 🧘
I generally think that timezones are an outdated and unnecessary concept for anyone. If we fantasize, it's not quite clear what the problem is if in London sunrises and sunsets will be at the time like now, and in New York 5 hours later. But the clocks will show the same time both there and there. If a plane took off at 19:00 and flew for 4 hours, then it will arrive at 23:00 in whatever direction you fly, a blast right? Everyone will just live on one time and that's it.