No sources and not balanced - there was a lot of work done to combat Y2K, so maybe that mitigated the disaster scenario?

There are no sources linked or cited to support the author’s claims. Also, the author makes statements about software that are illogical. For example: “If one program passes bad data (like a bad year on date record), the other programs don’t stop working; they just error out the piece of data.” The author seems to be making a huge, illogical leap that computer systems can detect and recover from all errors. In fact, the error would only be detected if the developer codes for it. The point of fixing the Y2K issue was that developers did not think about this type of error. I supported end user computing technology in the years leading up to Y2K and personally saw software issues that had to be fixed (and were) for Y2K.

Definite lack of reliable sources in this article. Although the author claims that most relevant links from the time are no longer available online, he also states that most of the piece is written from personal memory. Writing from one's own anecdotal experience decades past is no way to inform readers about a very important moment in technology history.

One doesn't have to have been involved in the frenetic source-code clean-up required to ensure a bare minimum of critical infrastructure and try to avoid a calamity - or the fear and panic as the clock rolled - but it helps. Gluing together a story out of a massive technical issue and a proliferation of doomday cults created to con the weak is sketchy at best -- highlights a better motive for this piece.

I remember reading the well researched articles predicting nothing would happen, and I believe this gentleman was on Good Morning America, if I recall correctly. Great read for anyone who wants context on a historic occurrence of fake news media creating a false narrative that had complex and long lasting ramifications.