Today we travel to a future where software engineers didn’t actually fix any of the Y2K bugs.
What would have happened if we had ignored the problem? What lessons does Y2K have for us, and why are people worried about 2038?
Complete transcript available in site.
- Peter de Jager — author of “Doomsday 2000” and Y2K town crier.
- Dr. Andy Michael — geophysicist with the U.S. Geological Survey’s Earthquake Science Center
- John Feminella — engineering leader at ThoughtWorks
- Dr. Sara K. McBride — emergency management specialist with the U.S. Geological Survey
- Meredith Cornelius — Friend 1
- Arielle Duhaime Ross — Friend 2
- Lux Alptraum — Scientist
- Jayne Quan — Scientist
- Stan Alcorn — News Announcer
- Brent Rose — Nuclear facility head
- Matthew Pecore — Flight attendant
- ‘Here We Go. The Chaos Is Starting’: An Oral History of Y2K
- Y2K: An Autobiography — Peter de Jager’s podcast about Y2K
- The Town Crier for the Year 2000
- Expensive Y2K Bug Nibbled Away Millions
- Report: Y2K fix disrupts U.S. spy satellites for days, not hours
- Police computer turns teens into seniors with an attitude
- False Prophets, Real Profits
- Remember Y2K? Here’s How We Prepped for the Non-Disaster
- Parking Meters Are Rejecting Credit Cards in Y2K-Type Glitch
- A lazy fix 20 years ago means the Y2K bug is taking down computers now
- What is the Year 2038 problem?
- Epoch Time Calculator
- Warning fatigue : Insights from the Australian Bushfire Context (2014)
- Volcanic Hazards: Risk Perception and Preparedness
- The Big One: Your Survival Guide