Skip to content
The Y2K Bug: $300 Billion Hoax or a Disaster Narrowly Averted? artwork

The Y2K Bug: $300 Billion Hoax or a Disaster Narrowly Averted?

pplpod

October 8, 2026

In the year 2000, a 105-year-old woman in Oslo received a formal letter offering her a place in kindergarten. The Norwegian citizen registry stored only the last two digits of her birth year, so the computer read 95 and assumed 1995.

TopicsHistoryMusicMusic History

SPEAKER_1 (0:00)

So in the year 2000, there was this 105-year-old woman living in Oslo, Norway.

And she went out to check her mail one day. And amidst the usual bills and local ads, she finds this very official, very surprising document from the local government. It was a formal letter offering her a spot in a local kindergarten.

SPEAKER_2 (0:21)

Oh my gosh.

SPEAKER_1 (0:22)

I mean, that is a pretty jarring piece of mail for a centenarian.

SPEAKER_2 (0:25)

Right.

SPEAKER_1 (0:27)

And it happened entirely because of how the Norwegian Citizen Registry stored their data at the time. Their system, it only tracked the last two digits of a person's birth year.

SPEAKER_2 (0:39)

I see where this is going.

SPEAKER_1 (0:40)

Yeah. So the computer looked at her birth year, which was recorded as just 95, and it mechanically deduced that she was born in 1995, not 1895

SPEAKER_2 (0:50)

Because, I mean, the computer only knows the parameters it's given, right? And in this specific case, it was instructed that basically anyone with a 95 was a five-year-old ready for finger painting.

SPEAKER_1 (1:01)

Exactly. And that kindergarten letter is funny, but it's literally the exact same coding shortcut that just a few months earlier had people buying survival gear, hoarding gold, and waiting for the global power grid to just completely collapse.

SPEAKER_2 (1:15)

Yeah, it was wild.

SPEAKER_1 (1:16)

So welcome to this deep dive into the infamous Y2K problem, the year 2000 bug. We are cutting through the mythology today to answer a question that actually still divides people.

Was this turn of the millennium computer bug the biggest, most expensive hoax of the 20th century? Or was it like a catastrophic global disaster that was just narrowly averted by an army of unsung coding heroes?

SPEAKER_2 (1:41)

And I think the answer reveals an incredible amount about human psychology plus our deeply complicated relationship with the technology we build.

SPEAKER_1 (1:49)

Absolutely. And whether you actually live through the panic of 1999 and I don't know, hoarded bottled water in your basement, or you've only ever heard about Y2K as this weird historical punchline, the reality of what went down is just so much stranger than the myth.

SPEAKER_2 (2:04)

It really is.

SPEAKER_1 (2:05)

So to understand how the entire world got thrown into a total frenzy, we kind of have to travel way back in time, back to the incredibly mundane realities of computing in the 1960s and 1970s. We really have to look at the environment where this bug was actually born.

SPEAKER_2 (2:22)

Right. Because we are talking about an era when computers were, well, the size of entire rooms. They required these specialized cooling systems, and yet they possessed less total memory than a modern musical greeting card.

SPEAKER_1 (2:35)

Which is insane to think about.

Let's put some numbers to that because early computer memory wasn't just small, it was staggeringly, prohibitively expensive. So in 1975, a single kilobyte of memory could cost over $100.

SPEAKER_2 (2:50)

Wow.

Just to give you a modern point of comparison on that, a single high-resolution photo on your smartphone today takes up about 3,000 kilobytes. Okay. So storing just one of those photos in 1975 would have cost roughly $300,000.

SPEAKER_1 (3:07)

That is just, that's unbelievable.

SPEAKER_2 (3:09)

Every single character data was a massive financial investment. You really couldn't afford to waste a single byte.

SPEAKER_1 (3:16)

And because of that cost, data processing was often done on punched cards. Like these were literal physical cards made of stiff paper that had exactly 80 columns. You had exactly 80 physical spaces to record a piece of data. That is it.

So programmers were forced to get incredibly creative.

SPEAKER_2 (3:33)

They had to be.

SPEAKER_1 (3:34)

And one of the most obvious ways to save space was to look at a date, say 1975, and realize, hey, you didn't need the 19 You could just punch 75 and everyone knew what century you were in.

SPEAKER_2 (3:46)

Exactly. And saving those two characters on every single date entry across millions of financial or government records, that saved an enormous amount of money and processing power.

SPEAKER_1 (3:56)

Right.

SPEAKER_2 (3:57)

It was honestly an elegant solution to a very rigid physical limitation.

SPEAKER_1 (4:01)

See, that's the thing. I always hear people today call those early programmers lazy or like short-sighted. But I look at those constraints and I completely defend them.

SPEAKER_2 (4:10)

Oh, for sure.

SPEAKER_1 (4:11)

I mean, okay, let's unpack this. Think of it like this. Imagine you move into a tiny, incredibly expensive 100 square foot apartment in the most expensive city on earth. Space is at such a premium that you actually take a saw and chop the legs off your bed just to make it fit under a sloped ceiling.

17 more minutes of transcript below

Thousands of transcripts fetched by people building searchable podcast archives

Fetch the whole transcript

The demo key returns a sample episode in full, no card needed:

request
curl -H "x-api-key: pt_demo" \
  https://spoken.md/transcripts/1000651996090

Markdown with the speakers named, for your notes, your knowledge base, or anything that makes HTTP calls.

From $0.10 per transcript. No subscription. Credits never expire. Prices exclude VAT, added at checkout for EU customers. Not what you expected? Email us within 14 days with 20 or fewer credits used and we refund the pack in full.

Using your own key:

request
curl -H "x-api-key: YOUR_KEY" \
  https://spoken.md/transcripts/1000793884446