The Technology-god Is Mortal

1 Nissan 5786
Rosh Chodesh 

Y2K was not a joke, certainly not at the time.  I was working in the technology sector back then and I saw the feverish effort to thwart the threat up close.  I always recalled that it was an Israeli who came up with an idea for a fix (around October?), but in later years, when I would bring that up, people acted as if they had no idea what I was talking about.  It was apparently not widely known and was subsequently lost in the rush to portray Y2K as a laughable conspiracy theory.  

I remembered all this today when I came across this article in the JPost...

So, I asked Google AI the following question, below is its response...

"With regard to Y2K, I recall from the time period that an Israeli man found an actual fix and it was immplemented, forestalling any ill effects. Can you find a record of that and perhaps the man's name?"

Based on records from the late 1990s, the Israeli man you are likely recalling is Erez Dunietz, who developed a software solution called Sapir 2000.  (WIRED)

While no single person "fixed" Y2K globally—as it required the effort of hundreds of thousands of programmers worldwide—Dunietz's story was notable because he was not a formally trained computer scientist; he was an administrator at a Jewish university in Jerusalem who claimed to have found a "revolutionary" way to address the bug.

Key Details of the "Fix"

• The Software: Known as Sapir 2000, the program was designed to automate the process of finding, fixing, and verifying date-related code.

• Performance: In testing conducted by the Israeli Ministry of Science, the software reportedly fixed and verified 400 programs and 400,000 lines of code in just one month.

• Implementation: The solution was initially marketed to the local Israeli market by Magic Software Enterprises, with plans for a global rollout if it proved viable.

• The Context: At the time, Israeli institutions were investing heavily in Y2K preparations, with major banks spending over $100 million combined to ensure their systems were compliant.

It is important to note that while Sapir 2000 was a significant local success, the overall "forestalling of ill effects" was the result of a massive, decentralized global effort that involved rewriting legacy code (like COBOL), implementing "windowing" (treating years 00-20 as the 2000s), or replacing hardware entirely.  (National Geographic)

HKB"H saves us even from ourselves.

~ CHODESH TOV ~