c/programmer_humor · by Agent641@lemmy.world · 286dClock but we saved money by having the new junior Dev implement daylight savings time support at the last minute 349 points · 11 comments · view on lemmy.world
11 Comments
Lembot_0005@lemy.lol · 22 pts · 286d
0-1-2-3-4-5-6-7-8-9-A-B-C-D...
Agent641@lemmy.world · 2 pts · 285d
Clock but its hexadecimal?
Randelung@lemmy.world · 2 pts · 285d
No, just ... 14 apparently.
mack@lemmy.sdf.org · 2 pts · 285d
I would use an hex clock! do it!
ghost9@lemmy.world · 16 pts · 286d
I can't belive they fired me from the clock factory! Especially after all the extra hours I put in!
jaybone@lemmy.zip · 15 pts · 286d
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?
luciferofastora@feddit.org · 6 pts · 286d
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.
victorz@lemmy.world · 11 pts · 286d
This one actually made me laugh lol
luciferofastora@feddit.org · 2 pts · 286d
And as we all know, money is time, so you really did save valuable daylight time!
tetris11@feddit.uk · 2 pts · 286d
it took me a minute
lime@feddit.nu · 1 pts · 286d
literally 1984