I never got upset when someone found a problem in my code, but I did get irritated when my boss didn't read it because he trusted me. "Even Jove nods."
________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Bob Bridges <[email protected]> Sent: Friday, July 29, 2022 10:48 AM To: [email protected] Subject: Re: Mainframe outage affecting W.Va. state agencies could take 48, 72 hours to resolve Inbox Some of my favorite military authors talk about the dreaded post-battle analysis, in which a board sits on the officers involved and asks lots of penetrating questions: Why did you make that choice? If the enemy had done this, what would have been your options? Did you receive intelligence notification SR-45T, dated such-and-such, about the enemy's new tech, and did you take that into account when you arranged your forces? I understand why it feels to the victims as if the purpose is to spread blame around. But this is the time to look at everything that happened and see what should have been done differently. It's a great time to answer honestly "in the press of the moment, I never thought of that option", and "our logs show that we received that communication, but I don't recall it". Blame, shmame; the board presumably knows what happens in "the press of the moment", and this is my best opportunity to improve my decision-making. (Which sounds heroically rational, but I still get all defensive during coding reviews.) --- Bob Bridges, [email protected], cell 336 382-7313 /* How bad is our traffic mess?....Gridlock is so bad that as many as 15 percent of women drivers now pass the time by picking their noses. (The figure for men remains steady at 100 percent.) -Dave Barry, 2004-10-17 */ -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Grant Taylor Sent: Friday, July 29, 2022 01:19 This is exactly why I *LOVED* the extra time at the end of the coordinated D.R. Test window. We had extra hardware, we had copies of our systems (if we did our job correctly) and no threat of an outage. I thought it was *GREAT* that we could test things /after/ the D.R. Test results were declared but before people went home. Lots of learning and experiments happened in those 36-48 hours. --- On 7/28/22 3:22 PM, Bob Bridges wrote: > Belated comment: I got a couple of laughs out of this post originally, > but it might be well to realize that these stories are not of failures. > This is why we do DR tests. It'd be a failure if you have an actual D > and found you couldn't R. > > So we try it out ahead of time, discover what we don't know, and > repeat as necessary. That discovery is success, not failure. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
