Hacked - Throwback: The Year Double Zero

Episode Date: December 31, 2022

Oh dang we have enough episode to do reruns. We promise we'll use this power responsibly. To ring in New Years, please enjoy this throwback Hacked about the y2k bug. Learn more about your ad choices. Visit podcastchoices.com/adchoices

We have never done a rerun before, but I was very excited to revisit this episode about Y2K. It will be 2000. So we rebooted and started properly making the show three years ago now, which is very weird. And two years ago, at the end of that first year making it consistently, which back then meant like once a month, we did an episode about Y2K. It was a subject I was very excited to learn and talk about. It was honestly one of the first ones we did that flexed a bit outside of the cyber security beat. And listening to it now, I am struck by a bunch of things. First, there's some different music that we don't use anymore, and I miss some of it.

But the big thing was how much the story of what happened at the dawn of the year 2000 felt relevant to what we had just experienced over the course of 2020. but kind of remixed almost. Like Y2K was a problem that was predicted and handled so well that people thought that it wasn't a problem to begin with. It was retroactively dubbed hysteria when in reality institutional responses were so thorough. They basically addressed the problem before it became. 2020 was kind of a negative image of that or like a remix.

It had all the same elements in a totally different order to completely different outcomes. We certainly had not predicted the problem well enough to prevent it, but it was a big problem that required this massive coordinated response to address, and it's hard not to see shades of one story in the other. Together they kind of constituted almost a set of case studies of what it looks like when you manage to solve a problem before it becomes one, and what it looks like when you do not,

which is the conclusion I think you hear us wander, up to by the end of the episode. I hope you enjoy the rerun. And you will see pandemonium. Listen to him. I hope you enjoy the rerun. It was a lot of fun to make. I got to watch a whole wild Leonard Nimoy computer documentary, which if you're bored,

you should hunt down on YouTube. We are taking the holidays off, so y'all get a rerun. But we're going to be back in a few weeks, and in 2023, my resolution is that we keep just widening the scope of stories about technology that we tell. And to tell some that aren't just about hacking into stuff, but hacking things together, making cool new stuff, and still a bunch of stories about people hacking things apart. Thanks for listening this past year.

Hope you enjoy this hacked throwback, year double zero. We'll catch you in the next one. This takes place on a day back in the year 2000. And on that day, A technician from the National Reconnaissance Office is sitting at their computer terminal. It's their job to monitor the feeds from a collection of spy satellites, live images captured by the satellite, piped back to their offices in Virginia for collection and analysis.

24 hours a day, seven days a week, crystal clear images from around the world populate these screens. And on this day, all at once, the technician watches as the feeds from five satellites, turn to static. Nothing. No more images, no more video. All five satellites are now feeding them an endless stream of what would later be described as garbled nonsense. Now, up until that day, the Pentagon had never disclosed to the public when a spy satellite had malfunctioned. And that day was going to be no exception.

They held no announcements, they posted no releases. There was no sign that anything had gone wrong with the hardware. So for four days, the NRO worked in secrecy digged. through the software, trying to figure out what was corrupting the signal from these five satellites. For four days they looked and they fiddled until finally, one by one, they were able to bring the spy satellites back online. It's worth mentioning that on the same day, back in 2000, the exact same time of day, other strange things were happening all around the world.

In Japan, for two minutes. a danger alarm began to fire at a nuclear power planted Onagawa. Luckily it was a false alarm. In Sheffield, in the United Kingdom, 154 pregnant women received emails with incorrect medical data about their children. In upstate New York, a man received a bill for $91,000 because his VHS rental of the John Travolta thriller, The General's daughter, showed up in the store's rental system as being 100 years overdue. years overdue. All around the world on the same day as the clocks bore the exact same time,

things were going just a little bit funny. You know what time of day that was? 12.01 a.m. January 1st, 2000. No surprise. These global issues are the direct result of an equally real human oversight. Many people now refer to as the Y2K or year 2000 problem. Depending on who's you ask, and importantly when you ask them, the chaos preceding Y2K was either apocalyptic hysteria, an international grift by the software consulting industry, or a hard-won lesson, in the idea that if you solve a problem well enough, people will question whether or not it was a problem to begin with. This episode's going to come out right around New Year's in that weird little window of time between Christmas and New Year's Eve in the twilight of a pretty crappy year.

So we're going to dive into the most famous New Year's in recent history, where the public at large was finally forced to reckon with how entangled with technology our world had become. And what it might mean for all of that technology to collapse, out from under our feet, right as the clock struck midnight. This is the year double O, here on Hacked. When I get out here in these speeches and hearings and other press, presentations, the first thing that comes up is that people say, say, how do we get into this mess? My first question is, where were you on Y2K? Cool, where was I on Y2K?

It was a long time ago, Jordan. Scott out at the bar? I think I was. I had probably just, I think I was out at the bar. I think I had just turned of age, which ages me, and I don't really know if I want that in the episode. I was also at the bar. bar, don't worry. I was nine, so it was a little bit weird, but people were cool about it. They thought the world was going to end. So which of those three do you think it was? I think it was all three,

truthfully. Yeah. Like that, I think that they did a really good, there was a lot of resources committed to dealing with that issue. And I think that they did solve it in enough systems, and they did solve it well enough that it seemed like it wasn't a big deal after the fact. if you discount all of the work that went into preparation for it. But also, a lot of software consulting companies made a pile of money. So I don't know if you call it a grift. Yeah. But definitely was probably a very lucrative time to be in the development industry.

I think that's a pretty good bird's eye view of where we're going. The way we get there is pretty interesting, but I think that's kind of where this all ends up shaking out too. It's interesting that you have that much insight into this because my sense of Y2K has always been like really superficial. I think because I was really young when it happened and I never really appreciated how much concern there was and how much money got spent on it. Oh, oh loads. Heaps. So it starts back in 1959 with a woman named Grace Marie Hopper and an invention called Cobal. The story of Y2K really begins several decades ago back in the 50s with a very enterprising woman.

by the name of Grace Murray Hopper. Her nickname was Amazing Grace because of all the outstanding accomplishments in her life. One of her accomplishments was the invention of the compiler for computer programs, which translates regular written language into the ones and zeros of binary code. Maybe even more importantly,

Grace Hopper was centrally involved in the creation of Cobol. What is Cobol? Cobal is a programming language. The old school language that you don't run into, anymore or you probably still do truthfully in the right corners of the world. And if you're a COBOL program or you probably get paid a boatload of money because

it's probably only a few hundred of them left. I think what surprised me about COBOL and really the lifetime of that language and a few others like it was just how long it existed for. Like Grace created it in 1959 and it was in widespread use well into the internet era. And when she wrote it, they were using punch cards. And I have no way of knowing if she knew how long Cobol and other languages like it were going to be in use. But for that entire window of time, like decades and decades and decades, people were writing stuff in Cobol. The programs that I think they probably thought were going to be replaced.

Of course, they thought they were going to be replaced. Everything was short-lived. You know, mankind's, you know, got a real blessing of short foresight. And I think this entire bug is based on that short foresight. in the primitive days of computers mainframes relied on the use of holleryth cards which were cardboard cards with holes punched them to create computer programs

they operated computers sort of like the way an old piano scroll would create music on a player piano and they didn't really realize that these programs were going to be persisting for decades and decades and decades even as a lot of other things about computers were changing so when she wrote it she was using punch cards which have 960 bits to them. Right now, I go to B&H.com.

I can buy 32 gigabytes of DDR4, 3200 megahertz memory. The kind of computer power you can now get on a laptop. It used to require a system that was so large. It literally had to be housed in its own building. And I did some math, which is always really dangerous because I have an English degree. But there are eight bits, a zero into one in one byte. And there are a billion bytes in a gigabyte,

which means eight billion bits in a gigabyte, which means for 150 bucks, I can buy 256 billion bits of memory. And Grace had 960 on a punch card. Which is all to say that for a really, really long time memory was at a super high premium. And odds are pretty good. If you were one of those people writing software, you were writing it in a very budget, conscious storage medium. So as more and more COBOL programs, totaling into millions, and eventually billions, were written on Hollerith cards. the sheer expense of computing began to really add up.

And the other thing is that you didn't really know how long it was going to live for. So in the 1960s, memory is still in an insane premium, and the people writing these cobalt programs start to figure out ways to conserve space to be a little bit more cost effective, to get down the number of zeros and ones that they're using. And so over the years, 1965, 1966, 1967, this really obvious question emerges. Every time we write the year in our programs, we're wasting two whole bits writing 19. So to save space, let's write 65, 66, and 67, because they all start with the 19.

And so for years and years, as the world has becoming computerized, people all over the world are writing these programs. Programs that run power supplies and satellite communications and water and health care and transportation and food delivery. For 40 years, the world is being written in. into this new set of languages like Cobol, languages that could do things that old ones couldn't. And the year is always being written in two digits. I think mankind has always looked to shorthand things. It's one of the things we do, we do it well,

is that we figure out more effective ways to communicate the same information. So short-hending our years to just the latter two digits of the year was always super easy to do and everybody did it. It wasn't, I wouldn't say it was just a programming thing. I'd say that most people did it just generically. And I think the big problem here was that, you know, they were probably writing these pieces of software thinking that they would be upgraded or removed or replaced within a few years or maybe a decade.

But lots of businesses got ingrained business systems that lasted for 20, 30 years. So, you know, something that was written in like 1975 is now going to be, you know, still operational in 2000, which is kind of crazy. The distinction between normal software and a database was also really really. really, really surprising to me. Like, I didn't realize how different they were and how much longer a database can live that it can survive multiple iterations of the software wrapped around it. Yeah, well, I think the big thing is databases, even if you change the software application, the data storage itself, because databases are so structured, you can migrate the data. And so, you know, data that was created a system ago, you know, in a completely different platform,

probably was just transferred to the new system. You know, it was migrated over. So lots of that data, you know, be it, you know, utility records or whatever, health care records, you know, have probably lived on for decades, even though they've gone through a system or two. We've gotten really good at migrating data. So this problem then emerges. Because come 2000, according to all of these programs that have been living a lot longer than

people originally thought they would. Program is using just the last two numbers to represent the year. What year is it? So in the year 2000, and they knew this at the time, you would have zero, zero pop up, not two-oh-oh-oh. So the computer thinks it could be 1900. Oh-oh-oh. And if they think that they've leapt backwards 100 years to the year 1900, or even thousands

of years to the year zero, do they keep working? So yeah, we may have saved a lot of money by eliminating those two digits, but here we are 40 years later, and the cost to correct problems because of this omission is in the trillions of dollars. That's the Y2K problem. That's the Y2K problem. This sort of cultural realization that for decades we'd been building this whole modern

society on a foundation of software that as this theory went, come January 1st, 2000, is going to do something unpredictable. and potentially really, really bad. The bigger thing here is that I don't think the computers really care about what year it is, right? So you just have to look at the year value as strictly numerical. So the problem becomes anything that's looking at date ranges or previous is, like, you know, everything before a specific date, all of a sudden anything in the zero-zero's is now a previous.

Lots of access, authorities, things like that are all date stamped, timestamps. So, you know, all of that stuff could potentially break because all of a sudden it's going to see it as anything that was given out in, say, 1999 that has a two-year expiration, all of a sudden, zero, zero, it's going to be invalid. So there's just so many checks and balances that use date and use it in a mathematical sense, and all of that stuff would probably stop working. At a tough time identifying exactly when people started getting worried about this, but I think the best indicator might be when they start spending money on fixed. and the answer is like pretty late in the game.

I think it was like a mid-90s like realization. Mm-hmm. And I'm pretty sure that's why it became a panic. Yeah, of course. I've got to say that like I think it was like 90 after 95. Like I remember it became a real frenzy in like 97 and 99. We're gonna spend a lot of time hanging out in 1998 because that's when some like major figures show up on the scene. Yeah. So these companies are now starting to finally spend a little bit of money, hire, computer programmers and software consultants to go digging through all of their systems.

Any software, any integrated chip, any machine really, looking for any instance of a two-digit year. Which seems, at least to me, it seemed like relatively straightforward as bugs go. Until I considered the sheer like scope and scale of what they had to dig through. Every line of code for every piece of software. Yeah, pretty substantial. There's the conspiracy theory we talked about. the start of the show that the Y2K problem was a griff from the software consulting industry.

And I don't I don't really buy that in terms of causality. I think it's a little bit too simple. But I do get how people get there. Because when we talk about like, oh, we spent hundreds of billions of dollars on Y2K, they're the people that a lot of that money was being spent on. Yeah. I wanted to do a bit of a section here about what it is that they were doing. If you were one of these software engineers, how do you squash the Y2K?

bug when you find it. The reality is that every piece of date code, so anything that's referencing dates, accessing dates, storing dates, ranging dates, you know, looking and comparing dates, anything that touches any kind of date field has to be updated.

Because you remember that like all the computer sees is a set of integers, right? It sees 63 or 81 and all of the code that says if, you know, variable date is less than 90, our current date value of 98, you know, then do this. You know, anything that looks at those date numbers had to be reviewed, updated, changed, and checked, and any date stores, so in the databases and all of this legacy data, you know, your cell phone bill or not your cell phone bill then, I guess, would have been your, well,

it might have been your cell phone bill, but the, you know, your phone bill from 1987 that's stored in some crazy text database somewhere, probably had a two-digit date year. So they either have to update the databases to add the one-nine to the front of it, or they'd have to write code that on like pulling those date fields, you'd have to prepend the one-nine to them. So you'd have to do so much, you'd have to literally make a huge map of all your data, figure out where dates are, figure out how dates are used in all the code, and then go in and fix every little piece of that, which is.

what those software consultants got paid boatloads of money to do. So the purest option, you just talked about the first two, was something called date expansion, which is what you said. It's you manually expand a two-digit field to include the century. Yeah. You do that across everything. And that's great because it's permanent and it's easy to maintain, but it takes forever so it costs a lot of money.

Totally. Your other option, which you talked about, is date windowing, where the programs determine the century value only when it was needed for a certain function. Only when you need to know the year does this little thing tack on those digits. But this one's not permanent because every time you add new functionality, you also have to update the windowing. But it was cheap and it worked in a pinch. Third one is something called date compression. And date compression is where you compress the date down into a binary 14-bit number, which is like the event horizon in that sentence where I stop understanding what it means.

And last, there were pre-built solutions. Essentially, software companies that would sell software kits to people or companies. These seem like varying shades of grifty, but it's hard for me to tell from looking at them. This date compression one sounds more interesting. Yeah, I don't really get how I understand the sentence that you compress the date down into binary 14-bit numbers. To do that properly,

you'd still have to go through all of your pre-existing dates and data and update them because I imagine it's compressing them down with the 19 before them. Just so that when you get to the 10, 2000s and 2001's the binary numbers shows that it's, you know, of greater value than 1987. I feel like the only context, and there might be an exception of this, but would be instances where memory was still at a premium. Otherwise, if you're going in and you're finding every instance, you can just do a date expansion. Well, that's the, that's the other big costly thing

here is that any kind of like embedded systems, so things that are like literally on chips and built into hardware, you know, running pumps and valves and stuff like that. Those systems like PLC stuff would be super annoying to have to go around and update every single, you know, HVAC control system and things like that. Like just, can you imagine how many of those are installed in the field and then have to go around and do a software update on every single piece of integrated chip hardware? Like, oh my God. Computers talk to one another.

information is transferred from one system to another. And if that information is not transferred because the computer in question doesn't understand the change of date, if the data that is transferred is affected by a date and causes a loss of integrity of that data. And if this all seems like a lot of crap to have to deal with

on one computer or machine, imagine when they start talking to, each other. The problems just multiply when stuff gets networked. In other words, the FAA year ago, had a problem with the radar system. Took it into the laboratory, thought they'd fixed it, just looks great, worked great. They got it into a tower. And when you suddenly have thousands of interactions from airplanes and everything else, people problems, you name it. And it didn't work. In these systems that were built long before 2000, you know, any kind of network transmission was probably, you know, very constructed, like they transferred the exact

information between each other. They had defined bytes, like these bytes are the date, this byte is the instruction, these bites are the notes or message or whatever. And all of that transmission data would have relied on the size value of the date field being a specific length. And then when you increase that, you know, naturally all of a sudden, the thing that's reading the network packets from the other systems has no idea what's going on because it's, it doesn't know that it's a year, it doesn't know anything. It's just looking at lengths. And all of a sudden, lengths are different. That type of interconnection is really the basis of the problem of Y2K. So time keeps winding down shorter and shorter. And the amount of code keeps getting

longer and longer. And so by the time the clock runs out, we find ourselves holding like a bill for a rush job, essentially. When the American government really started ringing the alarm, it's about 1998. The Clinton administration appointed a guy named John Koskinin to run their counsel on the year 2000 conversion, and a lot of their efforts focused on, you know, doing the obvious thing, incentivizing companies to spend the money and do that costly testing and review. It was really this big, massive mobilization costing billions of dollars. And it was really really, unfolding really right up until the last second. And so that's sort of how the government and companies responded to solving the problem.

But it's really only half of the story of Y2K because we haven't really gotten to how people responded. And that's the like, it's the good stuff. The bug in our cultural software, our beliefs about the millennium, we're much more serious than a technical problem. Right after the break. Think about the last time you heard a breach story on. on this show. It always starts the same way. Someone, somewhere, saw something too late, an alert buried, a signal missed, an SOC that just couldn't keep up. Arctic Wolf set out to solve

that problem by rebuilding security operations from the ground up for a world where attackers are already using AI. They created the Aurora Super Intelligence Platform, a fully agentic system powered by the swarm of experts. Instead of single-purpose bots or lucky-guess LLMs, this swarm is full of deterministic agents that handle whole entire entire entire. entire workflows. Humans stay in the loop and on the loop to validate the critical decisions and keep everything trustworthy. And all of this is just off running on their secure operations graph. A constantly updating intelligence engine fueled by more than nine trillion telemetry events every week and over a decade of real world incident response. The system reasons on real

signals and real context not synthetic training data. And the result is the new Aurora agent SOC. It's the first SCC that is agent led by design. You get agents that coordinate, agents that investigate, agents that respond at machine speed, and hundreds more that automate the repetitive work that normally buries human analysts. Arctic Wolf didn't try and bolt AI onto an old model. They rebuilt the model entirely. What makes it even more effective is how it works with Arctic Wolf's concierge experience. The team brings customer-specific context directly into the platform so every AI-driven decision reflects your environment instead of generic assumptions. The automation frees your concierge security team to focus on higher-backer.

strategy and proactive risk reductions while the agents handled the grind. If you want to see what trustworthy, production-ready AI insecurity operations actually looks like, go to arcticwolf.com slash hacked. Ever feel like cyber threats are evolving faster than anyone can keep up? Last year, 2025 was nothing short of a record-breaking year for major breaches, from sophisticated ransomware operators to AI-enabled attacks that turned defenses on their head. Organizations around the world saw headlines they never expected and cybersecurity teams were tested like never before. But here's the thing. These incidents aren't just news headlines. They're learning opportunities. And that's why Arctic Wolf is hosting a live webinar on February 5th diving to the most impactful

breaches of 2025. Their field CTO and security leaders are going to unpack not just what happened, but why these attacks succeeded. And most importantly, what businesses can do to fortify their defenses for it's too late. You're going to walk away with real insights and how threat actors are evolving. how defenders are responding, and what strategies can help you stay ahead of the next big breach. It's not fearmongering. It's practical, actionable, intelligence from experts in the trenches. Register now at arcticwolf.com slash hacked. Let's go back to 1999.

Come the year 2000, many computers will assume zero zero. Means the year 1900. Back to the future. I think it's fair to say that if a bunch of governments and corporations start spending money, frantically trying to avoid a looming crisis, that that is newsworthy. And the media should probably be covering that. But in order to cover that spending, they have to explain the emergency.

It's a very serious emergency covered very seriously. And as a result, and I benefit from a lot of hindsight here, a whole bunch of dominoes kind of fall. First off, nervous people tune in. So the media keeps covering it because they like when people tune in. And the temperature of the whole situation rises a little bit. And some people, a small minority at first, get really, really scared. And they start running out and buying bottled water and seeds.

And some of them start building bunkers. And so the media covers that. And the temperature rises a little bit. And then a bunch of people go, like, man, I wasn't nervous before, but I don't even have canned food, let alone a bunker. And it rises a little bit more. And then some other people start seeing all of this alarm and they think I like money and they start selling a solution.

And to sell that solution, you have to sell the problem more, rising the temperature further. And before you know it, you've now not only got this problem that you're paying billions in consulting fees to solve, but you've got total panic. It was always a concern to me that the panic would spread. Because once you start warning people and scaring them, it's a little hard to get them off the leg. But we're ahead of the story. It's 1999 and people are losing their minds. And this is where we'll play a montage of people losing their minds. Surf through the internet these days and you keep coming across a strange new word, Tiotow Waki.

The word stands for the end of the world as we know it. Erie North has his own natural gas well. He says it's his ticket for survival. That cheers me up. Scammers praying on a confused public. He said, yeah, I'm calling from Bay Boston. And I need to get decals now to you. you put them on your credit card, they won't work after Y2K.

I believe that Y2K may be God's instrument to shake this nation, humble this nation, awaken this nation, and from this nation, start revival that spreads the face of the earth before the rapture of the church. People thought it was literally end of days. Will it be a nuclear power plant? Will it be the airplanes in the sky? Will it be the food supply change, transportation? There are so many possibilities.

Until that day finally arrives. The ball is beginning to move. They can feel it. December 31st. 10. 9. 8, 7, 6. 5.1. The ball still dropped in Times Square. And everyone's still there.

Everyone's still alive. Lights didn't even go out of it. No, planes fell out of the sky. The power grid's still up. Goldman Sachs is still clicking along. Global finance is doing pretty well. So what the hell happened? The arrival of Y2K did not bring the much anticipated and feared computer meltdown. It appears to have been more of a prankster than a real problem. Things couldn't be going more smoothly. So smoothly, some are even asking if all that preparing was necessary. I have a theory about where the panic came from.

Let's hear it. It's a pretty roundabout one. You know the Drake equation. I do. Yeah. Drake equation is a probabilistic argument used to guess how many alien life forms there are. are in the universe. And based on the sheer volume of space and planets, the Drake equation suggests that there should be anywhere from 1,000 to hundreds of millions of civilizations in the Milky Way alone. And yet, we seem to be, everything's really quiet. And I think that's kind of

what happened here, at least in terms of the panic. Instead of planets, we had like almost infinite lines of code and chips and systems that had to be searched through. And they controlled such important things that if even a tiny fraction of those things went wrong, if even a tiny fraction of those planets had life, the world as we know it was going to be changed in this really intense way. Like odds were good, something should go wrong and yet nothing. So we come back to those three theories at the start of the show. Theory number one.

International grift by the software consulting industry. It was a big gold mine, like a gold rush for software consultants and patching and fixing and then analyzing and reporting. and verifying, you know, there was an endless amount of work in that time for that stuff. I get how people get there. Yeah, is a big deal. Imagine if you were a Fortune 500 company and all of a sudden all your financial systems are gone.

Imagine the loss of revenue per day, loss of value, loss of cash flow, loss of everything, it would be like critical. Of the untold fortune spent trying to avert this thing, it was spent on consultants and engineers, but I don't think that means they orchestrated it. Benefited, yeah, but engineered, no. It's like you could, I don't think it was orchestrated at all. And like the reality is, like, you know, we're currently in a health pandemic. And a lot of healthcare professionals are working more and getting paid and, you know, other things like that. Do we think that they orchestrated it? Like, that just seems like an insane theory. Yeah, it's almost like there's a lot of parallels.

anyway, which isn't to say that there were grifters and bad faith actors. Like there were there were grifters. There were people taking advantage. There were a lot of survival guys written, a lot of Y2K branded rations. But again, that's opportunism, not orchestration. Yeah, yeah. So I think if you want to get to why this happen,

you've got to keep looking. Which brings us to theory too. Cultural hysteria slash technophobic panic. I'd say this is like half of it. Oh, easy. Yeah. We talked about the media feedback, loop a little bit earlier. But the part we didn't discuss was this idea is really this idea

of computer literacy, which isn't to blame people back then for not seeing that everything was going to be fine because it might not have been okay. It's just to say that like for 40 years, the world had been changing. And suddenly people who had been taught how to like take apart a motor and shop class realized they didn't really understand the mechanics of how the world worked anymore. Like what was on the far side of every screen, every button, they just didn't really understand it. And so the story comes along telling them that it's all built on this ratchee foundation, that there's like a prophecy of its failure. It kind of makes sense. It sort of feels a little bit right. It's not that it's too complicated for me to understand. It's that it was

all too complex to begin with. So I'm going to buy some seeds and some land because planes are going to fall out of the sky. And then there's theory three. You never get credit for the disasters you ever overt. That you never get credit for averting a crisis that never happened. Especially if you're a programmer and nobody understands what you're doing to begin with. People like to point to the fact that a lot of nations that have computers and use computers didn't do anything to address Y2K and that they were generally okay, that they didn't spend the money, which means that everyone else wasted the money, which is initially intuitive, but not really how software worked in 1999.

Because if a computer being used in South Korea or Russia where they didn't spend the money keeps working, you can't just ignore the fact that those that didn't prepare were protected by the efforts of those who did. You can't ignore the fact that those places benefited from high-level software patches rolled out worldwide. I think this is a bit of a metaphor for the entire IT industry. It's like, you know, you have great IT when you don't know your IT people, you know what I'm saying? Like they're the unsung heroes because the only time you ever talk to them is when you're

mad at them. It's like the once in a while when something goes wrong, they're the ones that, you know, get whipped in and pulled in to come firefight the problem. But as long as everything's running good, I, you know, I worked in tech for a long time. And, you know, you don't, you don't sell them or you seldom get a Friday message being like, hey, Scott, you know, everything was great this week. Like I didn't have to talk to tech once. And, you know, just, you guys just do such a good job.

Thanks. it's like you never get that message. The only message you get is the one, you know, Sunday at 9 p.m. being like, my printer is not working or I can't connect to this or, you know, what happened to this. The firewall is not letting me in to access my computer, you know, things like that where, you know, it gets escalated in people. So I think this is one of those things where it's like, it's just another example of like the tech people doing something and doing it well enough that they just don't get any recognition for it. I think the frustrating thing about this theory, and there's like a lot of frustrating stuff, those satellites that crashed at the top of the show actually crashed because of a Y2K software

patch, not because of Y2K. But frustrating part about this theory, and I think that this theory is true, is that no one can say that they know exactly what would have happened if things that happened differently. Yeah. Like no one can really say with certainty that things would have been okay because we, we didn't allow for that situation to happen. Of course, preparedness dealing with adversity. The Senate's final report on Y2K found that government and industry did successfully avert a crisis

at an estimated cost of $100 billion, which was only the American response and a small sliver of the global spend which crept over half a trillion. I guess by crept over half a trillion, I mean $600 billion because $100 billion isn't really creeping. My answer to people who said, well, I wasted a lot of money was the number of things that happened that went wrong that fortunately were around the edges demonstrated that you didn't fix the systems, it wouldn't work automatically. The report also said that in hindsight, knowing what we know now, that these efforts did divert crises. Did they overspend potentially? IDC's Project Magellan 2000 report estimated maybe about 30% overspending, but that's again really hard to guess. Not everything that was fixed needed to be fixed.

That's fair to say. Apparently a lot of embedded chips kind of would have just kept clicking along, okay. But Koskin and that guy we've heard from throughout the episode is adamant that these little things that happened around the fridges. You know, the one hospital's medical record sending out false reports instead of thousands. The one guy with the crazy $100,000 VHS rental bill. Those really raise a question of if that's what's left over after we spent half a trillion dollars, what would have happened if we hadn't. Totally.

We have little Y2Ks happening all the time. Technologies are always created for one reason, but end up being used for an application that the creator can never imagine. It's been really interesting reading about this. And I think that there are like a lot of lessons in this story. They're murky and they're frustrated by competing information, but they are buried in there. I think the reality is that,

I think for a lot of things, you know, business management systems and probably a lot of the people that got paid, the crisis that was averted was probably more of a reporting crisis because like a lot of reports would have miscalculated because, you know, like the, what was the example you had of the guy who got a bill for like $10,000 for his BCR rental? Because I thought he had it out. John Travolta General's daughter. It would have been like those kind of crises. It wouldn't have been in like most of the cases. But then there's a lot of other things where, you know, critical systems are sending information back and forth. And anything like dates are typically used for validation

and anything that would have invalidated because the date field was wrong would have been a big problem. But anything that was like more of a reporting thing, I think the crises would have been pretty, you know, soft tissue. I think that there's lessons about how we have a really bad habit of waiting until the last minute to solve a problem and how much worse problems get when we wait. I think there's lessons in the feedback loop about how a problem becomes a panic in culture and media and how alternatively, like, dangerous the pessimism that that breeds can be the next time we have to

solve a problem. And here's the thing. For however silly like Leonard Nimoy sounds in this episode, and I really, really like Leonard Nimoy, and it was hard. Hard to listen to those clips. The lesson isn't really to ignore like these big problems that we, don't understand. I think the lesson is to endeavor to like understand them so that we can do the right things so we can solve them properly. I think when the feed from a satellite comes back

garbled, you don't just shrug and say like, oh, I guess that proof satellites were dumb and it's going to begin with. Like you hunker down and you solve the problem. Totally. So let us use the Y2K challenge as an opportunity to reflect on where we're headed as a civilization. Perhaps the most important opportunity we've ever had. If the omission, of two simple digits can have worldwide impact several decades after its inception, we must ask ourselves before we rush too far forward, what are we doing now in genetic engineering? With cloning, with the development of bacteriological warfare life forms, with death-ray technologies and pollution of land, air, and water that could have long-term, unpredictable worldwide effects.

And what can we do as the inheritors, the caretube? of this world. What can we do to protect our home, our island in space? Thanks for listening, everybody. If you want to support the show, you can check us out at patreon.com slash hacked podcast. Some folks were very generous this month. Jimmy Cochran, your support means the world to us. That's patreon.com slash hacked podcast. You'd find us on Twitter at hacked podcast. We got our archival for this episode from a few different sources, 1999's Y2K Family Survival Guide with Leonard Nimoy. It's really good. It's on YouTube. You should check it out. The New York Times, much to do about nothing retro report.

And ABC's New Year's Eve 2000 original coverage. Thank you for listening, everybody. This has been about a year back after a big hiatus, and it's been a lot of fun. Looking forward to what 2021 brings. Stay safe and have a happy New Year's.