InBash_DevOps_AIbySabit·Oct 28The One Date That Will Break Linux Systems in 2038Epoch time explained, plus how to check the date range of your own machineA response icon3A response icon3
Robert Broeckelmann·Jun 26The Year 2038 Problem: When Computers Discover Time Is HardFor most of human history, keeping track of dates was relatively straightforward. The sun came up; the sun went down.
Jiya·Jan 15The Epochalypse — Why Every 32-Bit System is Secretly a Time BombThere is a strange confidence we have in time. We assume computers understand it because they’re so good at tracking seconds.
Séв(aѕтιen) L. ⚠·Dec 30, 2025Le “bug de l’an 2000” n’a pas échoué, il a été vaincuLe mythe est confortable : le bug de l’an 2000 aurait été une hystérie collective, un fantasme de journalistes technophobes. La vérité est…
Victor Apeland·Nov 6, 2022My screensaver is a countdown to digital doom.Integer overflows, 70’s technology, planes falling out of the sky, and the screensaver that shows it all.
Gerry Martinez·Jul 7, 2021The Year 2038 effect? What is the Year 2038 problem?The danger of a technical meltdown owing to the dreaded “Effect 2000” or “Millennium Error” sparked considerable panic in society in 1999…
Prince Francis·Aug 8, 2020Processing time in c/c++ — solution for year 2038 problem in 32 bit machineHow to find the difference between 2 dates, which are in string format ?
InLevel Up CodingbyEdward Childress·May 16, 2019Problem Solving IIThe Year 2038 ProblemA response icon1A response icon1
Edgar Gonzalez·Jan 13, 2016End of time: Jan 19th, 2038Time as we (engineers) know ends on January 19, 2038–03:14:07 UTC (Year 2038 problem)A response icon1A response icon1
