ViperGeorge
Enthusiast
I want to thank the webmaster and others that are working to return our club site to its previous glory. However, as someone that has spent my career in Technology leadership I would humbly suggest that major upgrades like this should have been thoroughly tested prior to implementation. There are reasons why we move new software to Quality Assurance environments and User Acceptance Testing environments prior to implementation. It allows us to verify that the change that we are about to make in fact operates as intended. It is not necessary to replicate the production environment fully, as this would be expensive, but installing the new software and testing it first makes a heck of a lot of sense. It should have been easy to identify that this change was going to have major impacts to the site. Naturally we also attempt to over-communicate on major changes to make sure that our customers/users are anticipating the change and what impacts it might have.
Even in the corporate world we occasionally run software that is no longer supported by the vendor or otherwise is out of date. This is not a reason to jump into an upgrade without thorough testing. The software worked yesterday and will most likely work today and tomorrow. (Rare exception is when a vendor builds in an expiration date based on license renewal.) When we make major changes to our web site we set up an alternate URL and allow a group of internal users to bang away at it to test it. We would not move it to production until we were reasonably confident of the outcome.
Again, I know that folks are working hard to fix the various problems and I'm not trying to be overly critical here. Life will go on and the VCA will survive this little hiccup with the website and I'm sure that future upgrades will be much more seamless.
Even in the corporate world we occasionally run software that is no longer supported by the vendor or otherwise is out of date. This is not a reason to jump into an upgrade without thorough testing. The software worked yesterday and will most likely work today and tomorrow. (Rare exception is when a vendor builds in an expiration date based on license renewal.) When we make major changes to our web site we set up an alternate URL and allow a group of internal users to bang away at it to test it. We would not move it to production until we were reasonably confident of the outcome.
Again, I know that folks are working hard to fix the various problems and I'm not trying to be overly critical here. Life will go on and the VCA will survive this little hiccup with the website and I'm sure that future upgrades will be much more seamless.