Runtime Arguments episode 37 explores the Unix Year 2038 problem—when 32-bit signed timestamps overflow on January 19, 2038—and compares it to Y2K, arguing both represented reasonable engineering trade-offs for their era given storage constraints. The hosts discuss how 64-bit systems and modern kernels (Linux 5.6+) have largely mitigated the issue, then catalog real-world overflow bugs spanning GPS week counters, NTP rollover, Boeing 787 generators, NASA probes, and date-handling flaws in Excel, PlayStation 3, and Microsoft Zune.
A discussion of the Unix Year 2038 problem, where 32-bit signed timestamps overflow on January 19, 2038, alongside historical context comparing it to Y2K and examining how engineering trade-offs made sense given era constraints. The episode covers mitigation status across systems, similar overflow bugs in GPS/NTP/databases, and real-world failures like NASA's Deep Impact probe and Sony PS3 bricking, concluding with reflections on writing maintainable code.