§ 04 · News & references
The reading room.
The Year 2038 problem has a decade of press coverage behind it and a shelf of good reference material. This is ours: fourteen pieces we actually return to, explainers for new engineers, warnings for executives, and incident reports that show the failure modes are real. Every link leaves this site; the one-line summaries are ours.
Reference & explainers
The starting shelf: accurate mechanics, neutral tone, useful in a kickoff meeting.
-
01
Wikipedia — Year 2038 problem
The standard overview: the epoch, the overflow arithmetic, affected systems, and remediation history. Where every client conversation starts. en.wikipedia.org
-
02
PCMag Encyclopedia — Year 2038 problem
A tight definition entry — the right length for forwarding to a non-technical executive. pcmag.com
-
03
Linux Foundation — Torvalds monitoring the Year 2038 problem
A window onto how the open-source kernel community has tracked Y2038 for years — the time64 groundwork is a decade old, and it started upstream. linuxfoundation.org
-
04
Versus — The Year 2038 problem
An accessible explainer that puts the overflow in plain terms before the arithmetic does it in stone terms. versus.com
-
05
Medium / Wesley Abbey — 2038: Y2K, Unix, and the End of Time
An engineer's long-form take on why the deadline keeps getting pushed downstream — the pattern our audit chapters describe, from the inside. medium.com
Press coverage & warnings
Mainstream attention began years ago. There is no longer an excuse to say to management that the window for "we didn't know" is long closed.
-
06
The Guardian (2014) — Is the year 2038 problem the new Y2K bug?
The piece that carried the deadline into mainstream technology coverage a decade before it bites. theguardian.com
-
07
SecurityWeek — The Y2038 bug is a vulnerability, not just a date problem
The security framing we use with boards and CISOs: rollover breaks certificates, trust chains, and audit integrity — not just clocks. securityweek.com
-
08
Popular Mechanics — Y2K, Y2020, and the calendar bugs of computing
A press retrospective on the arithmetic-of-time problem — useful for showing that the pattern of deferred fixes repeats. popularmechanics.com
-
09
Tom's Guide (2017) — The 2038 bug
Consumer-facing coverage from the Black Hat security conference: the problem entered the tech press years before it entered procurement. tomsguide.com
-
10
Hawaii News Now (2022) — 'What Tech': 2038 problem is real, threatens digital infrastructure worldwide
Regional broadcast coverage reaching past the technology audience — and accurate about the infrastructure angle. hawaiinewsnow.com
-
11
Interesting Engineering — Modern computers might stop working on January 19, 2038
A headline that still reads like alarmism — and still describes a real arithmetic ceiling. interestingengineering.com
-
12
Independent Australia — Year 2038: the day we run out of time
Policy-column treatment of the same deadline from outside the US tech press — useful for international stakeholders. independentaustralia.net
Incidents & engineering notes
Time faults reported as operations stories rather than curiosities. These are the pieces we cite when a plant team says the rollover is theoretical.
-
13
The Register (2024) — IT Incident Report: the clock that got ahead of itself
An incident write-up in the Register's best tradition: a synchronization failure handled as an operational failure — root cause, blast radius, and the lesson. theregister.com
-
14
Hackaday (2025) — The Epochalypse: Y2K, but 38 years later
The hardware-hacker community's framing of the rollover — the layer where people still write time code by hand, and where the fix actually starts. hackaday.com
How to read this coverage
A recurring theme across a decade of articles: the pieces aimed at
consumers describe the ceiling correctly and then imagine it
arriving in phones and laptops. The systems that meet it first are
the ones that don't make headlines, the RTU commissioned in 2015
for a thirty-year service life, the motion controller counting
milliseconds in time_t, the historian driver compiling
32-bit conversions nobody has re-read since.
Read the press list for the awareness history; read the standards shelf on Our Approach for the compliance framing; read The Problem and the vendor field notes for what actually has to happen, in what order, on a plant schedule rather than a news cycle.
News articles won't audit your fleet.
Reading the same deadline from different mastheads is a start. Reading your own register is the deliverable and we can begin that this quarter.