From Y2K to 2038, Lessons Learned from First Computer Crisis
It’s hard to imagine in these days of smartphones, iPads, and Google Glass that something called the Y2K bug threatened to topple technology, upset the economy and wreak general havoc at the close of the 20th century. But it did. Survivalists bunkered down. Preachers predicted the apocalypse. And ordinary folks wondered if any of it was real.
Was it? Was the Y2K bug a genuine threat – or just a hoax? And what did it all mean? To get some answers, Retro Report tracked down key players in this millennium drama – like Paul Saffo, a technology forecaster, author and consultant who first alerted his clients to the Y2K issue in the mid-1980s; and John Koskinen, the government’s Y2K czar, who directed the battle against the bug. They provide a riveting look at the problems then – and the implications now. We better get our ducks in a row because the 2038 bug is coming our way (maybe).
More Like This
Google Workers Walked Out Over Harassment. A Year Later, What’s Changed?
Sexual harassment. Discrimination. Workplace inequity. Google’s employees demonstrated against unfair practices. One year later, has anything changed?
Lessons From the Challenger Tragedy
Normalization of deviance, the process of becoming inured to risky actions, is a useful concept that was developed to explain how the Challenger disaster happened.
Could We Geoengineer Ourselves Out of Climate Change?
Is geo-engineering the climate an answer to global warming? Cold War science has some lessons.
Are Robots Really Taking Over?
Humans are wary that robots could replace them. So what can we learn from the legendary chess match between a supercomputer and Garry Kasparov?