Due to the panic, this solution was implemented: Companies and governments invested billions of dollars in updates and fixes to avoid chaos. Programmers and technicians worked at a rapid pace to adapt systems and avoid problems at the turn of the millennium. But what really happened was that, in practice, the Y2K bug didn't cause the expected catastrophe. There were some isolated failures, such as at bus terminals in Australia and measuring equipment in Japan, but most systems worked properly. The successful resolution of the problem was the result of a global prevention and remediation effort.
What can we learn from this is:
The Y2K bug taught some important lessons, such as the need to plan and invest in technology, the importance of collaboration between different sectors, and awareness of the risks of computer system failures. But there are other bugs in the future ahead of us, as computation is not entirely perfect: So It's important to emphasize that date-related problems still exist in computer systems. The so-called "2038 Y2K bug," or Y2038, linked to the time standard in Unix systems, could affect systems using 32-bit systems starting in 2038. Again, the expectation is that upgrading to 64-bit systems, which have a much higher limit, will prevent future problems.
Posted Using INLEO
Congratulations @moriame! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOP