Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@landoncolburn
Mostly, because time of day literally dependent on location.
The better alternative to timezones is to use UTC everywhere. We don't all start work at the same local time anymore anyways. So doesn't really matter whether high noon is at 12 or 2. -
@landoncolburn
Well, that is the real question here.
Why do people insist on noon being roughly at 12am, white colars commonly to start work at 9am and end at 5pm?
There seems to be a strong believe in numerology or something like that - the numbers themselves have to be what they are for some unknown reason... -
@Oktokolo noon was the time were the sun has its highest point.
-
@stop
I know.
But that it has to be on 1200 is a completely unneccessary rule.
It actually changes during the year anyways (yes, daylight saving time exists, but that is a really blunt tool too).
So why not just use UTC - and accept that noon and work times are at different time of day in different locations. -
@landoncolburn Well cause politics i guess. Just look at Australias weird bullshit with DST and half hour timezones.
when your code is a mess but everything work out in the end
When you keep getting +1s on a rant you posted a month ago.
Go big or go home.
I worked on a feature that included setting a cookie to expire in an hour.
QA: The cookie’s time should be set to my local time.
Me: What the—are you kidding me?!The cookie’s exp time is in UTC. Whether you’re in NY or Singapore, that cookie will expire an hour from when it’s issued. Now stop flagging non issues and beta accept my ticket.
This is the weirdest s*** QA has pulled.
devrant
rant
qa problems
are you kidding me?
wtf