When there were (almost) no issues at the begin of 2000, it was because of a lot of concentrated work correctly done before, early enough. The luck was that the problem was in the consciousness of everybody making decisions, and that those making decisions had a good motivation to do the changes (e.g. the company can charge for fixes, or the company will not be able to sell the product if it's not fixed).
The real danger is when those who make decisions (and those who directly influence them) have a good motivation (from their narrow point of view) to continue ignoring the problem.
That's how the environments described by Octavia Butler develop.
I like following the creators of the stuff I enjoys but Adams is proving to be a challenge for me. I should have stuck with the "never meet your hero" mantra.
I worked on adjustments in cobol code for the y2k bug in accounting systems. We had to start well before, because contract with payment in the future did not work. Cobol at that time had no date type and stored the data as 3 integers, day, month and year. The job was basically to redo the calculation of terms adding 100 to year when it was greater than 00 and less than 50. (2000 to 2050). Anyway, who had a system susceptible to the bug, had no option but to make adjustments or lose their payment controls.
Edit: ading 100 to year, not 2000