5 ms·
2010 bug hits millions of Germans
- Timothee 17y agoDoes anyone know what the nature of the bug is? The article lacked on this aspect unfortunately.
- ugh 17y agoNone of the many German articles I read about the topic mentioned the exact nature of the bug.
- ABrandt 17y agoMy first guess would be that the software somehow recognized "2010" as "1910". Not sure exactly what dating structure would lead to this though.
- aarongough 17y agoPerhaps they thought they would improve on the 2 digit method of representing years, and used a single digit method instead? ie: 2009(9) -> 2010(0) I would be pretty sad if it was a bug as obvious as this though. No idea what the real bug is likely to be...
- sp332 17y agoI thought this was discussed earlier this week, but I can't find a link anywhere. The representation of the date is ambiguous about decimal/hexadecimal. So some devices are reading "10" as equal to 16, yielding the year 2016 instead of 2010.
- please 17y agoas a workaround one can put a strip of tape over the chip, that way the magnetic strip on the other side gets used.
- 83457 17y agoThe dreaded Y2.01K Bug
- zb 17y agoActually, Y2k01. Engineers don't use decimal points - it's too easy for them to disappear during copying.