Hacker News Reader

Comment by eru | Hacker News Reader

That seems a bit silly to me? That's a problem that occurs every years twice; so we should write code to automate it instead of dealing with it by admin hands.

View on HN

The problem is we have to keep updating that code when the rules change.

Servers which miss that patch break because of various Auth schemes which require clocks to be reasonably in sync between machines.

So you get a bunch of outages whenever the next time shift is post-rules change.

I am less annoyed with DST than I am at how often we are fucking with it and breaking stuff.

I like it when the US fucks with time zones. The more you fuck with time zones, the more likely US-based developers are to just say fuck it, we'll use a library. The more developers that use a library for time zones, the fewer pieces of software that I have to deal with that get this wrong for my part of the world.

(Did you know Australia has 11 possible time zones of which up to 9 are being used right now? It might even be 12. Most people don't, which is why most programmers fuck it up)

> The problem is we have to keep updating that code when the rules change.

Yes, indeed. But we also have to change what people do manually when the rules change.

remember this is a industry that thinks run fast a break things is a good motto. is it any wonder that the same people that need reminding that name fields should accept non latin character and that passwords should in fact be more than 8 characters would consistently fuck up something that only comes up twice a year.

I used to work with a system that 'conveniently' silently dropped leading and trailing space in its password field (and also just copied the password into an https-URL without any encoding, so no special characters for you). The guys who committed this crime thought that only weirdos like me have such strange passwords..

Reply on news.ycombinator.com