As per the article, one of my major clients was dead in the water this week when their IT team rolled out updates to their system which included upgrading Chrom

As per the article, one of my major clients was dead in the water this week when their IT team rolled out updates to their system which included upgrading Chrome on all PC's in the office. They are a broker agency for a major financial institution, and all of a sudden, they could not log in to their major vendor's financial transactional system - because it was secured with a GeoTrust cert that didn't have the appropriate root chain and was thus rejected by Chrome. Complete stop. In many ways, much worse than the whole Y2K thing. The parent financial institution had no idea about the cert, and it wasn't until I sent an email to their IT department that they realised what had happened (because internal tests (with different browsers or older Chrome versions) were still working fine). It is getting to the stage where we need to have some sort of overriding, holistic approach to managing these sorts of issues and upgrades. It is too easy to think everything is ops normal if you aren't using a particular browser or framework etc. I fully admit that we are guilty of this too - we only test our web development work on a narrow subset of browsers and hope for the best. That target is getting smaller and smaller every day.