I lost an argument when I worked at a very large discount broker in San Francisco.
We had a big upgrade going in with a complex back out process. I said we should install and immediately back it out to test the backout scenario. Senior people scoffed at the idea. In went the update and boom! It went pear-shaped. The backout process didn't work too well and we spent way too many hours getting stable. Test everything, even backout. On Mon, Jul 22, 2024 at 7:21 AM Steve Thompson <[email protected]> wrote: > Some of us that worked for good companies that wanted our > products to be bullet proof (as much as we could make them) did > that level of testing -- specifically with tape drives until SCSI > came along and everything went virtual (still had cartridges in > those machines). > > And M/S should be doing that level given the damage done this > past week. > > Just my opinion. > > Steve Thompson > > On 7/21/2024 1:07 PM, Paul Gilmartin wrote: > > On Sun, 21 Jul 2024 10:49:04 -0400, Phil Smith III wrote: > >> <snippage> > > Has anyone explained how this passed CrowdStrike integration test? > > > > But these things happen. I heard of a product that crashed > > reproducibly at customer sites having 8 or more tape drives. > > Who does that in a test lab!> > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
