Any Sufficiently Advanced Technology Indistinguishable From 01 January 1970

The talk opens with the speaker's memories of Y2K, when his father's worry about the date change shaped how he saw the event. He argues that the feared outage was largely prevented by quiet remediation work that few people noticed, since successful maintenance rarely draws attention. Press coverage and a technology boom had also inflated the hype at the time.

Attention then shifts to the 2038 problem, when the Unix time counter that started on 1 January 1970 overflows in February. Using a long-running "threat landscape 2038" thought experiment, he argues that cybercrime cannot keep rising indefinitely, so the future will look different from current trends. The main concern is embedded equipment such as traffic controllers, which often use cheap timing circuits selected through lowest-bid procurement. He asks what their state machines might do if their clocks report a wrong year, and notes that many of these electronics come from a concentrated supply source.

He closes by saying he has long waited for someone to show a solved approach and has not seen one. Between now and 2038, he says, operators need to sample fielded devices and test how they fail in a lab. For practitioners, the takeaway is to inventory long-lived embedded systems and plan testing now, rather than after the deadline arrives.