Striker@lemmy.worldM to Mildly Infuriating@lemmy.worldEnglish · 1 year agoThis mofo was born on the wrong daylemmy.worldimagemessage-square44fedilinkarrow-up1387arrow-down126
arrow-up1361arrow-down1imageThis mofo was born on the wrong daylemmy.worldStriker@lemmy.worldM to Mildly Infuriating@lemmy.worldEnglish · 1 year agomessage-square44fedilink
minus-squareChocrates@lemmy.worldlinkfedilinkEnglisharrow-up5arrow-down1·1 year agoYeah… I am stoned but this looks like it should be valid and there is just a bug in the code.
minus-squaredukk@programming.devlinkfedilinkEnglisharrow-up6·1 year agoI’m guessing the UI designer accidentally put in DD/MM/YY, when the code handles the date as MM/DD/YY.
minus-squaretimkenhanlinkfedilinkEnglisharrow-up10·1 year agoSometimes if the developers don’t specify, the date format can follow clients’ settings, which can lead to unpredictable results like this.
minus-squaredukk@programming.devlinkfedilinkEnglisharrow-up2·1 year agoYeah, I’d imagine you’d want to adapt for different locales. Here in the US, MMDDYY is pretty ubiquitous, but I’m sure it’s different in other countries.
minus-squaretimkenhanlinkfedilinkEnglisharrow-up2·1 year agoI’ve experienced this kind of confusion first hand, so I know a thing or two.
Yeah… I am stoned but this looks like it should be valid and there is just a bug in the code.
I’m guessing the UI designer accidentally put in DD/MM/YY, when the code handles the date as MM/DD/YY.
Sometimes if the developers don’t specify, the date format can follow clients’ settings, which can lead to unpredictable results like this.
Yeah, I’d imagine you’d want to adapt for different locales. Here in the US, MMDDYY is pretty ubiquitous, but I’m sure it’s different in other countries.
I’ve experienced this kind of confusion first hand, so I know a thing or two.