§ 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.

R.1

Reference & explainers

R.2

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.

  1. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

R.3

Incidents & engineering notes

R.4

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.

Housekeeping Every item above links to a third-party site — content, availability, and cookie behavior are theirs, not ours. Summaries are written by Year2038.net; dates reflect what the URL or the outlet's own archive indicates. Specific claims made by external third parties are not a claim year2038.net

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.