Aprogrammer_humor·Programmer HumorbyAgent641 Clock but we saved money by having the new junior Dev implement daylight savings time support at the last minuteView original on lemmy.world349Comments11Reply
gghost9 lemmy.worldI can't belive they fired me from the clock factory! Especially after all the extra hours I put in!16Reply
jjaybone lemmy.zip1Hide 1 replyWhat was that azure cloud bug where they added 30 to the number of days in a month to renew an SSL cert, and then February came along?15Reply
lluciferofastora replyfeddit.orgI find it hard to believe that they wouldn't be using their existing tools for handling dates and times. Surely MS have reasonable time handling logic, right? Excel thinks 1900 is a leap year and they won't fix it for legacy reasons Maybe not.6Reply
lluciferofastora feddit.orgAnd as we all know, money is time, so you really did save valuable daylight time!2Reply
11 replies
0-1-2-3-4-5-6-7-8-9-A-B-C-D...
Clock but its hexadecimal?
I would use an hex clock! do it!
No, just ... 14 apparently.
I can't belive they fired me from the clock factory! Especially after all the extra hours I put in!
What was that azure cloud bug where they added 30 to the number of days in a month to renew an SSL cert, and then February came along?
I find it hard to believe that they wouldn't be using their existing tools for handling dates and times. Surely MS have reasonable time handling logic, right?
Excel thinks 1900 is a leap year and they won't fix it for legacy reasons
Maybe not.
This one actually made me laugh lol
And as we all know, money is time, so you really did save valuable daylight time!
it took me a minute
literally 1984