Striker@lemmy.worldM to Mildly Infuriating@lemmy.worldEnglish · 2 years agoThis mofo was born on the wrong daylemmy.worldimagemessage-square45fedilinkarrow-up1402arrow-down127
arrow-up1375arrow-down1imageThis mofo was born on the wrong daylemmy.worldStriker@lemmy.worldM to Mildly Infuriating@lemmy.worldEnglish · 2 years agomessage-square45fedilink
minus-squaredukklinkfedilinkEnglisharrow-up6arrow-down1·2 years agoI’m guessing the UI designer accidentally put in DD/MM/YY, when the code handles the date as MM/DD/YY.
minus-squaretimkenhan@sopuli.xyzlinkfedilinkEnglisharrow-up10·2 years agoSometimes if the developers don’t specify, the date format can follow clients’ settings, which can lead to unpredictable results like this.
minus-squaredukklinkfedilinkEnglisharrow-up2arrow-down1·2 years 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-squaretimkenhan@sopuli.xyzlinkfedilinkEnglisharrow-up2·2 years agoI’ve experienced this kind of confusion first hand, so I know a thing or two.
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.