Bankenstein to Programmer [email protected] • 1 year agoXKCD 1172feddit.deimagemessage-square15fedilinkarrow-up1105arrow-down10cross-posted to: [email protected]
arrow-up1105arrow-down1imageXKCD 1172feddit.deBankenstein to Programmer [email protected] • 1 year agomessage-square15fedilinkcross-posted to: [email protected]
minus-squarehannes3120linkfedilink13•1 year agoExcel wrongly assuming the year 1900 was a leap year for their timestamps is my favorite bug that will never be fixed because everyone has built workarounds for this already
minus-squaretjhart85linkfedilink6•1 year agoDidn’t they do that intentionally to be compatible with Lotus 123?
minus-squaretjhart85linkfedilink1•1 year agoThanks for backing me up :-) A link from MS as well, backing us up :-)
Excel wrongly assuming the year 1900 was a leap year for their timestamps is my favorite bug that will never be fixed because everyone has built workarounds for this already
Didn’t they do that intentionally to be compatible with Lotus 123?
they did
Thanks for backing me up :-)
A link from MS as well, backing us up :-)