????Visit https://surfshark.com/bukidani and get 4 extra months of Surfshark at an unbeatable price!???? ♦ FOLLOW OTHERWISE ♦ ????Facebook: / bukidaniyt ????Instagram: / buki_daniyt ????TikTok: / buki_dani ????Twitch: / buki_dani ????Discord: / discord #netlegends #y2k #dani Have you ever been in a car accident? Time seems to slow down around you as you realize you're about to hit the car in front of you. It's too late to try to avoid it - you're going to crash. All you can do is watch. The IT community is racing towards an event worse than a car accident. We're heading towards the year 2000. Towards a complete upheaval of our familiar calendar system. Unfortunately, unlike a car accident, time is not going to slow down. If anything, we are moving faster and faster towards catastrophe. These are the apocalyptic sentences that begin Peter De Jager's 1993 article in the American magazine Computerworld, which was simply titled: Doomsday: 2000. The problem he outlined stemmed from a very simple mistake, or perhaps we should put it this way, laziness. In order to increase computing capacity, computers stored years in two digits. The problem was that many lines of code, many calculation tasks automatically assumed that the year should be supplemented with 19, so that if it had to be arranged in order or counted with it, these numbers would definitely follow each other. However, when the year 2000 comes, the two-digit year suddenly becomes zero. The computer does not understand that this new zero zero is BIGGER than all the numbers that have come up until then, because it has not been taught this, and it is only starting from mathematics. The problem sounds trivial, and it was really just that there was a solution that seemed easier than typing in the whole year all the time, and no one thought about what would happen when the millennium ended. Well, of course they did, but they just brushed it off. In 1993, however, when Peter De Jager wrote his article, it was no longer possible to postpone it. By then, they had already reached the point where they had to actively work on assessing the size of the problem, finding out which systems it affected, what error possibilities it had, and how much it would cost to fix it. Not to mention that there are predictive systems that calculate the future, such as those dealing with work schedules or salary distribution, which can use dates after 2000 as early as 1996... According to initial estimates, the largest companies will have to spend 50-100 million dollars just on programmer hours - PER COMPANY. It's a bug fix worth hundreds of millions, even billions of dollars, and who knows if there's enough time left. But Jager was the first to sound the alarm that this couldn't be put off any longer. In the following years, this problem was called many different things: Century Date Change, or CDC, Faulty Date Logic, or FADL, but the most popular name was simply the abbreviation of the year: Year Two Thousand, or... Y2K Support with a channel membership! / @buki_dani ????You can find more top lists in this playlist, you're sure to find something you like! ???? • Top lists, selections ????????And here you can find our previous Lore videos, if you're more interested in these:???????? • Lore videos, game stories ☝☝ Subscribe to our channel so you don't miss our other videos! ☝☝ LEET, LEET Hungary, game, video game, gaming, video games, games, Hungarian, dani, büki, büki dani, y2k, disaster, disaster movie, net legend, net legends, net legend, net legends, 2000, New Year's Eve, computing, virus, scandal, mishap, bill clinton, lieutenant spock, star trek, computer, bug, hack, hacker, error, computer bug, computer error, error code, this is how we avoided the end of the world